Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
On 01/02/2012 08:49 AM, Chad wrote: On Sun, Jan 1, 2012 at 12:49 PM, Brion Vibber bvib...@wikimedia.org wrote: I'd like us to plan for a code freeze on trunk -- at least a feature refactoring freeze -- starting within a few days to give us all a chance to tidy up, catch up with code review, and prepare for deployments. +1 I believe we've got some general plans to hit deployment in February; if we hit code slush this week or so that gives some time for everybody to catch up on review, do more thorough testing and -- perhaps most importantly of all -- make sure we have good documentation on what's changed and what needs to be tested and tried out by real humans! Sounds good. Want to say Friday's the date to be feature complete to give people the rest of this week? -Chad Questions about today's freeze (from Niklas, Roan, me in IRC): on what -- all of trunk? core? wmf extensions? 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? 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]? -- Sumana Harihareswara Volunteer Development Coordinator Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
On Fri, Jan 6, 2012 at 9:38 AM, Sumana Harihareswara suma...@wikimedia.org 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 doing. 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. -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
On Fri, Jan 6, 2012 at 9:44 AM, Chad innocentkil...@gmail.com wrote: On Fri, Jan 6, 2012 at 9:38 AM, Sumana Harihareswara suma...@wikimedia.org 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 doing. 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 deadline ;-) -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
I'll still be doing some work on FileBackend like fixing jenkins, cleaning up the streamFile() function, copying the swift backend to /trunk, and tying up a fix loose ends and doing fixes next week. I think heavy stuff is pretty much out of the way. -- View this message in context: http://wikimedia.7.n6.nabble.com/Rolling-towards-1-19-scheduling-a-code-freeze-tp2722998p3310386.html Sent from the Wikipedia Developers mailing list archive at Nabble.com. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
On Tue, Jan 3, 2012 at 2:05 AM, Erwin Dokter er...@darcoury.nl wrote: Can someone have a look at bug 25697, which is a very minor, easy patch? I hope to get this one in before 1.19, to go along with the new diff look. Done. Roan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Rolling towards 1.19... scheduling a code freeze
On Sun, Jan 1, 2012 at 12:49 PM, Brion Vibber bvib...@wikimedia.org wrote: I'd like us to plan for a code freeze on trunk -- at least a feature refactoring freeze -- starting within a few days to give us all a chance to tidy up, catch up with code review, and prepare for deployments. +1 I believe we've got some general plans to hit deployment in February; if we hit code slush this week or so that gives some time for everybody to catch up on review, do more thorough testing and -- perhaps most importantly of all -- make sure we have good documentation on what's changed and what needs to be tested and tried out by real humans! Sounds good. Want to say Friday's the date to be feature complete to give people the rest of this week? -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
