Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ESR Tracking/Landing Proposal
17 views
Skip to first unread message
Alex Keybl
Feb 9, 2012, 3:31:26 PM2/9/12
to mozilla.dev.planning group
Dan Veditz and I sat down recently to put together a proposal for tracking/landing fixes for the ESR. The main focus of the proposal was to make it as lightweight as possible for both developers and release drivers, while ensuring timely landing of fixes.
Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
-Alex Keybl
Release Manager
[1] https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
-Alex Keybl
Release Manager
[1] https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
Johnathan Nightingale
Feb 9, 2012, 3:42:53 PM2/9/12
to Alex Keybl, mozilla.dev.planning group
On 2012-02-09, at 3:31 PM, Alex Keybl wrote:
> Dan Veditz and I sat down recently to put together a proposal for tracking/landing fixes for the ESR. The main focus of the proposal was to make it as lightweight as possible for both developers and release drivers, while ensuring timely landing of fixes.
>
> Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
>
> [1] https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
> Dan Veditz and I sat down recently to put together a proposal for tracking/landing fixes for the ESR. The main focus of the proposal was to make it as lightweight as possible for both developers and release drivers, while ensuring timely landing of fixes.
>
> Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
>
Looks good to me. And way to anticipate my question about "why are we using mainline version numbers?" :)
J
---
Johnathan Nightingale
Sr. Director of Firefox Engineering
joh...@mozilla.com
Steve Fink
Feb 9, 2012, 4:45:23 PM2/9/12
to Alex Keybl, mozilla.dev.planning group
And if I set status-esr10 to checkin-needed and put [autoland-esr10]
into the whiteboard, then I can forget all about the patch and as soon
as it gets approval (status-esr10 changes to n+), it'll just land by
itself, right? :)
On 02/09/2012 12:31 PM, Alex Keybl wrote:
> Dan Veditz and I sat down recently to put together a proposal for tracking/landing fixes for the ESR. The main focus of the proposal was to make it as lightweight as possible for both developers and release drivers, while ensuring timely landing of fixes.
>
> Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
>
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
into the whiteboard, then I can forget all about the patch and as soon
as it gets approval (status-esr10 changes to n+), it'll just land by
itself, right? :)
On 02/09/2012 12:31 PM, Alex Keybl wrote:
> Dan Veditz and I sat down recently to put together a proposal for tracking/landing fixes for the ESR. The main focus of the proposal was to make it as lightweight as possible for both developers and release drivers, while ensuring timely landing of fixes.
>
> Please review [1] and provide any feedback you may have. Remember - we're trying to solidify a process that we'll use for ESR10's life, and likely even ESR17. Thanks in advance.
>
> -Alex Keybl
> Release Manager
>
> [1] https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
> _______________________________________________
> Release Manager
>
> [1] https://wiki.mozilla.org/Release_Management/ESR_Landing_Process
> dev-planning mailing list
> dev-pl...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-planning
Alex Keybl
Feb 9, 2012, 4:51:46 PM2/9/12
to Steve Fink, mozilla.dev.planning group
I found [2] as a reference for auto landing, and actually heard about this first just yesterday. Once autolanding is fully vetted on non-release repos, we can consider making the process even more lightweight. I imagine the process would be something like
* Set tracking-esr10=?, status-esr10=checkin-pending, and [autoland-esr10:24535,23524]
* We set tracking-esr10=n+
* When n==mozilla-beta version, patches 24535,23524 are auto landed on the ESR, and status-esr10=fixed
-Alex
[2] https://wiki.mozilla.org/Build:Autoland
* Set tracking-esr10=?, status-esr10=checkin-pending, and [autoland-esr10:24535,23524]
* We set tracking-esr10=n+
* When n==mozilla-beta version, patches 24535,23524 are auto landed on the ESR, and status-esr10=fixed
-Alex
[2] https://wiki.mozilla.org/Build:Autoland
0 new messages