On Wed, Jan 18, 2017 at 10:58 AM, Dirkjan Ochtman <dirk...@ochtman.nl> wrote:
> On Wed, Jan 18, 2017 at 4:49 PM, Ben Kelly <bke...@mozilla.com> wrote: > > While things have stabilized since then we are in process of making a > major > > architectural change in order to support multiple content processes > > (multi-e10s). This will make it very difficult to uplift fixes. Once > the > > new architecture has stabilized we should be able to enable SW in the > next > > ESR. > > > > Thoughts? > > Maybe I'm missing context, but I find the notion of not-shipping > things on ESR that are available on the normal release channel pretty > strange. Maybe this is because I'm incorrectly assuming that the > majority of Firefox usage in the wild is not on ESR? Alternatively, is > Service Workers the only thing getting major architectural changes for > multi-e10s? (I would assume not.) If not, are we withholding all those > other things from the ESR channel, too? > Last I checked we do this all the time for new and potentially unstable things. For example, AFAIK we do not enable e10s on ESR. I have not heard if that will change for 52 ESR. I would expect not, though, since we are still rolling it out to the full population. I just don't think we can commit to providing stable security uplifts to ESR for a 9 months if our trunk version is completely different. Ben _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
