| 30 Apr 2026 |
hexa | talked to emily lange just yesterday and my impression was that major bringups are quite a bit more work than the regular security releases | 12:09:57 |
whispers [& it/fae] | ah interesting | 12:10:08 |
hexa | I mean, that 's simplar to firefox patch releases | 12:10:10 |
hexa | Redacted or Malformed Event | 12:10:15 |
hexa | but major firefox releases only rarely cause issues | 12:10:29 |
Emma [it/its] | oh god, jesus christ | 12:10:44 |
vcunat | "demands of modern web". A weird way to justify that, or maybe I don't have any idea what modern web is about. | 12:13:19 |
vcunat | Generally with SW I'd say that specific people want updates early (perhaps just a specific new feature) but vast majority of people want less frequent major upgrades than they get. | 12:15:47 |
hexa | you don't? it's the slopfest. | 12:16:30 |
Emma [it/its] | i see this release cadence increase as a negative for the web tbh | 12:17:16 |
hexa | https://firefoxci-websocktunnel.services.mozilla.com/us-west1-a.6255730980504403819.60099/log/LEPLWp_ORUCRBAk1t_cvrg | 13:00:21 |
hexa | symbol scraping test run | 13:00:24 |
| 1 May 2026 |
| llakala set a profile picture. | 17:12:29 |
colemickens | Can I get an assist/consult here: https://github.com/nix-community/flake-firefox-nightly/pull/62
the fix seems okay-ish but I'm surprised that this wasn't noticed earlier.
I would expect to see something that updates where the devedition version is fetched, but that's not in the PR.
Surely it's not the case that every valid devedition build tag is also a valid beta tag so.... ??? | 17:41:37 |
whispers [& it/fae] | devedition and beta are released in sync and are basically the same browser | 18:36:26 |
whispers [& it/fae] | * devedition and beta are released in sync, versioned the same, and are in large part the same browser | 18:36:37 |
whispers [& it/fae] | * devedition and beta are based on the same branch, versioned the same, released in sync, and are in large part the same browser | 18:37:14 |
whispers [& it/fae] | * devedition and beta are based on the same branch, versioned the same, released in sync, and are in large part the same browser, so it's not surprising that it's just worked | 18:37:20 |
llakala | taking a look at where i re-import pkgs in my config - does the the usage of some wasm sandboxing in build-mozilla-mach really require an entire cross-chain?
relevant lines:
export WASM_CC=${pkgsCross.wasi32.stdenv.cc}/bin/${pkgsCross.wasi32.stdenv.cc.targetPrefix}cc
export WASM_CXX=${pkgsCross.wasi32.stdenv.cc}/bin/${pkgsCross.wasi32.stdenv.cc.targetPrefix}c++
and
wasiSysRoot = runCommand "wasi-sysroot" { } ''
mkdir -p $out/lib/wasm32-wasi
for lib in ${pkgsCross.wasi32.llvmPackages.libcxx}/lib/*; do
ln -s $lib $out/lib/wasm32-wasi
done
'';
| 18:56:57 |
llakala | * taking a look at where i re-import pkgs in my config - does the the usage of some wasm sandboxing in build-mozilla-mach really require an entire cross-chain, or is it possible to achieve this without it?
relevant lines:
export WASM_CC=${pkgsCross.wasi32.stdenv.cc}/bin/${pkgsCross.wasi32.stdenv.cc.targetPrefix}cc
export WASM_CXX=${pkgsCross.wasi32.stdenv.cc}/bin/${pkgsCross.wasi32.stdenv.cc.targetPrefix}c++
and
wasiSysRoot = runCommand "wasi-sysroot" { } ''
mkdir -p $out/lib/wasm32-wasi
for lib in ${pkgsCross.wasi32.llvmPackages.libcxx}/lib/*; do
ln -s $lib $out/lib/wasm32-wasi
done
'';
| 18:57:19 |
K900 | Yes, it does | 19:13:29 |
llakala | thought i'd ask. thanks! | 19:17:55 |
whispers [& it/fae] | * | 20:31:26 |
colemickens | great, that is basically the only explanation my brain could reason with, thanks for saying :) | 20:33:16 |
| 7 May 2026 |
nbp | https://groups.google.com/a/mozilla.org/g/dev-platform/c/LR5ovzj7ZkA/m/sfP65v0zAAAJ | 09:28:39 |
hexa | 2 years in the making | 09:29:26 |
hexa | Redacted or Malformed Event | 09:29:28 |
hexa | Redacted or Malformed Event | 09:29:30 |
hexa | this will further improve the details in our crashreports, which is much appreciated | 09:29:52 |
| @jykrwn_bot:matrix.org joined the room. | 09:32:41 |