On 01/02/2012 08:49 AM, Chad wrote:
On Sun, Jan 1, 2012 at 12:49 PM, Brion Vibber
<bvibber(a)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