A big milestone: 57 is now on beta, Nightly is 58 [was: Re: 57 beta cycle: 57beta/devedition published earlier + soft freeze]

2017-09-21 Thread Sylvestre Ledru
Hello, A quick update! I am sure you all know the schedule perfectly (right?) but I will repeat it again! We just merged m-c => m-b for the last time. We will start the 57.0b2 build in the next few hours which will be pushed only to devedition users (go and update it, you will see the cool new

Re: 57 beta cycle: 57beta/devedition published earlier + soft freeze

2017-09-13 Thread Kim Moir
Several releng folks, RyanVM and jcristau had a meeting today discussing tomorrow's merge We wanted to ensure that we would be able to have the correct branding for Fennec beta after the merge. In order to do this, we will have a relbranch created for Fennec on Sept 14 named

Re: 57 beta cycle: 57beta/devedition published earlier + soft freeze

2017-09-11 Thread Ryan VanderMeulen
In general, I would say your best bet is to have patches landed by mid-day PDT the day before if you want to be reasonably confident that it'll get merged over to Beta in time. Predicting when merges will happen is difficult due circumstances like build/test failures, infra issues, etc. It's

Re: 57 beta cycle: 57beta/devedition published earlier + soft freeze

2017-09-11 Thread Ed Lee
Is there any guidance on when commits should make it to autoland and inbound for both Merge Days (14th and 21st)? I suppose people should just get things in 24 hours before midnight 00:00 Pacific Time to be "safe" in case there's any bustages (hopefully reduced with the soft freeze). For some

57 beta cycle: 57beta/devedition published earlier + soft freeze

2017-09-07 Thread Sylvestre Ledru
Hello, tldr: we are going to do a first merge of m-c => m-b and use the devedition population one week earlier to push 57.0b1 & 57.0b2. In order to maximize beta testing, we are going to take advantage of the fact that we have a different set of users with the developer edition (which is, since