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.
> 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.
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? :)
> 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.
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
> 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.
