What Max said. I'm not a huge fan of code freezes generally speaking, I think they're a false sense of security and encourage developers to stack a lot more changes when the freeze is over...leading to more regressions than if you'd not frozen to begin with.
What I greatly prefer is code slushing...no big features or refactors, stick to small-ish bug fixing. That also answers Pine's question about what to do instead. -Chad On Tue, Nov 3, 2015 at 3:33 PM, Max Semenik <[email protected]> wrote: > How that is going to happen in practice? Deployment train will continue > functioning in December, as Greg says, so a full code freeze would mean no > merges into master - I don't think this is workable. > > On Tue, Nov 3, 2015 at 3:26 PM, Tomasz Finc <[email protected]> wrote: > >> Team and those that follow Discovery, >> >> We're exploring a code freeze for December in order to not conflict >> with any fundraising changes, respect everybody's holiday time, and >> provide some significant heads down time. >> >> The reading and editing departments are code freezing for the whole >> month and we could do the same. We could also free for just the last >> two weeks. >> >> Emergency changes could go through as long as Katie and Greg are ok with >> them. >> >> Eager to see what both the the team and public who work with us think >> >> --tomasz >> >> _______________________________________________ >> discovery mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/discovery >> > > > > -- > Best regards, > Max Semenik ([[User:MaxSem]]) > > _______________________________________________ > discovery mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/discovery > >
_______________________________________________ discovery mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/discovery
