Good idea, thanks for raising this! The split used to make more sense because we didn't have frequently-tagged builds, mostly because we didn't have great testing (so we had a lengthy manual test process before merging to master). Today though we have good testing (could still be better though) and a process for easily tagging builds, and we've had around one a week recently without major issue. So I think we can do this now.
Tasks for doing so may include at least: * Change the default branch on github, trivial. * Update docs - both on our website and others like https://webassembly.org/getting-started/developers-guide/ , pretty easy. * Update emsdk, probably easy (just the code for building from source, as getting binaries doesn't refer to a branch). * Update releases CI (auto rollers etc.). I'm not sure how that works. - Alon On Sat, Jul 20, 2019 at 9:11 AM Sam Clegg <[email protected]> wrote: > Is the separation of master and incoming serving in purpose? > > If not I'd like to propose that we move to landing new changed > directly on `master` and those who want stability can pin to a named > revision. > > Maybe I'm overlooking some utility that the split has? > > cheers, > sam > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAL_va29H6rcuwQwdJVf%2BSf%2B527AmMDMHvon133tt%2B9xBJv5_HQ%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpSwC1EpZObrC5yDBX-La%3D0bDx25UU6YyTjiYiwZa%3DUAqQ%40mail.gmail.com.
