innocentkiller at gmail
Jan 6, 2012, 4:11 PM
Post #5 of 6
On Fri, Jan 6, 2012 at 9:44 AM, Chad <innocentkiller [at] gmail> wrote:
Re: Rolling towards 1.19... scheduling a code freeze
[In reply to]
> On Fri, Jan 6, 2012 at 9:38 AM, Sumana Harihareswara
> <sumanah [at] wikimedia> wrote:
>> Questions about today's freeze (from Niklas, Roan, & me in IRC):
>> on what -- all of trunk? core? wmf extensions?
> Definitely core. Probably should apply to wmf-deployed extensions
> too. I think non-deployed extensions can continue doing what they're
>> So does that mean you have to stop adding features when Friday starts,
>> or ends? i.e. is Friday the first day of the frozen state, or the last
>> day of the non-frozen state?
> Let's give until midnight UTC, end of Friday.
>> Are we enforcing this in any way within SVN, or are we just agreeing to
>> quickly revert any new features or refactoring commits that come in
>> between now and [date]?
> No changes to access -- there's still legit reasons to commit things such
> as followups, regression fixes and the like.
> Remember everybody: we're calling this a "slush" and not an actual
> "freeze." The idea is to at least try and get trunk feature-complete so we
> can make the push in CR.
And it's now midnight UTC, pencils down everybody. If you were
looking to break trunk with a huge refactor...well, you missed the
Wikitech-l mailing list
Wikitech-l [at] lists