Re: Merge moved to Thursday 29th
1) The reason why we've merge in the beginning of the week is traditionally there has been fall outs as well as chemspills. ie this helps reduce the number of people that have to work weekends in order to fix up the branches. In case you need evidence of the fall outs, you can see the crash rates usually increase right after a merge. 2) There was an assumption that b2g would also move at this time and has moved master 2.6 prematurely; we still have not finished the project. As far as I know, taskcluster is not setup to make 2.5 builds. With the possibility of pvtbuild server going away,in the near future, this causes an issue to the B2G project. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
I missed two commits for 44 branch. https://treeherder.mozilla.org/#/jobs?repo=fx-team=6b3c99e54177 Uplift requests will not help because they are string changes. On 2015/10/29 5:10, Sylvestre Ledru wrote: > Hello, > > Because we want to synchronize the release of 42 and 44 devedition (next > Tuesday), > we are planning to perform the merge tomorrow, Thursday. > As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already > in release). > This will give us enough time to validate the first aurora build. > > I apologize for the very late notice. Of course, we will be friendly > with uplift requests. > > Sylvestre > > > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
Please request the uplift. Under specific circumstances (like this one), we take string changes in aurora. Thanks Sylvestre Le 29/10/2015 13:39, Masatoshi Kimura a écrit : > I missed two commits for 44 branch. > https://treeherder.mozilla.org/#/jobs?repo=fx-team=6b3c99e54177 > Uplift requests will not help because they are string changes. > > On 2015/10/29 5:10, Sylvestre Ledru wrote: >> Hello, >> >> Because we want to synchronize the release of 42 and 44 devedition (next >> Tuesday), >> we are planning to perform the merge tomorrow, Thursday. >> As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already >> in release). >> This will give us enough time to validate the first aurora build. >> >> I apologize for the very late notice. Of course, we will be friendly >> with uplift requests. >> >> Sylvestre >> >> >> ___ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform >> > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
I'm also commented in the bug: If we're doing uplifts, I'm not sure we're winning by uplifting pre-landed strings. Either way, I think the risk assessment of the patch should be that of the actual patch that uses the strings, not "just adding strings". Also, I'd appreciate an ETA for the patch, as that's also going in to the risk that a patch comes with. Axel On 10/29/15 1:41 PM, Sylvestre Ledru wrote: Please request the uplift. Under specific circumstances (like this one), we take string changes in aurora. Thanks Sylvestre Le 29/10/2015 13:39, Masatoshi Kimura a écrit : I missed two commits for 44 branch. https://treeherder.mozilla.org/#/jobs?repo=fx-team=6b3c99e54177 Uplift requests will not help because they are string changes. On 2015/10/29 5:10, Sylvestre Ledru wrote: Hello, Because we want to synchronize the release of 42 and 44 devedition (next Tuesday), we are planning to perform the merge tomorrow, Thursday. As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already in release). This will give us enough time to validate the first aurora build. I apologize for the very late notice. Of course, we will be friendly with uplift requests. Sylvestre ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
Le 29/10/2015 02:11, Ehsan Akhgari a écrit : > On 2015-10-28 4:10 PM, Sylvestre Ledru wrote: >> Hello, >> >> Because we want to synchronize the release of 42 and 44 devedition (next >> Tuesday), >> we are planning to perform the merge tomorrow, Thursday. >> As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already >> in release). >> This will give us enough time to validate the first aurora build. > > We've been working very hard to prepare Service Workers to be released in 44. > We're down to a few remaining bugs, and since we were hoping to get testing > on Aurora on this feature (hopefully with web developers experimenting with > it!) I have a couple of questions that would help us figure out > how this changes our plans (probably not in a great way!). > > It would be very helpful if we can get our last changes onto Aurora after > this uplift. What's the approval process involved? Is it the same as the > normal process? Yes. We are going to fast track the approvals. > > Also I think this essentially means that we would have no chance to get our > changes into the first Aurora build. So we would need to rely on the > updates. Are Aurora updates made nightly these days or are there small > "releases" on the Aurora branch? Aurora/Devedition builds are nightly builds. If you can get your changes into aurora Thursday or Friday, we can retrigger a build to make sure your changes are in the Tuesday release. Hope this helps, Sylvestre ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
Sylvestre Ledru wrote: Because we want to synchronize the release of 42 and 44 devedition (next Tuesday), we are planning to perform the merge tomorrow, Thursday. As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already in release). This will give us enough time to validate the first aurora build. I apologize for the very late notice. Of course, we will be friendly with uplift requests. please update https://wiki.mozilla.org/RapidRelease/Calendar and the associated ICS files. thanks. -- byron jones - :glob - bugzilla.mozilla.org team lead - ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
Please make sure to coordinate with the FirefoxOS release team since Gecko 44 is the release that will be used for FirefoxOS 2.5. / Jonas On Wed, Oct 28, 2015 at 1:10 PM, Sylvestre Ledruwrote: > Hello, > > Because we want to synchronize the release of 42 and 44 devedition (next > Tuesday), > we are planning to perform the merge tomorrow, Thursday. > As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already > in release). > This will give us enough time to validate the first aurora build. > > I apologize for the very late notice. Of course, we will be friendly > with uplift requests. > > Sylvestre > > > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Merge moved to Thursday 29th
On 2015-10-28 4:10 PM, Sylvestre Ledru wrote: Hello, Because we want to synchronize the release of 42 and 44 devedition (next Tuesday), we are planning to perform the merge tomorrow, Thursday. As a consequence, nightly = 45, aurora = 44 and beta = 43 (42 is already in release). This will give us enough time to validate the first aurora build. We've been working very hard to prepare Service Workers to be released in 44. We're down to a few remaining bugs, and since we were hoping to get testing on Aurora on this feature (hopefully with web developers experimenting with it!) I have a couple of questions that would help us figure out how this changes our plans (probably not in a great way!). It would be very helpful if we can get our last changes onto Aurora after this uplift. What's the approval process involved? Is it the same as the normal process? Also I think this essentially means that we would have no chance to get our changes into the first Aurora build. So we would need to rely on the updates. Are Aurora updates made nightly these days or are there small "releases" on the Aurora branch? Thanks! Ehsan ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform