Re: A new release process?

On Tue, Jan 3, 2017 at 1:32 PM, Jacob Champion wrote: > On 12/29/2016 08:16 PM, David Zuelke wrote: >> >> The tl;dr of this approach is that >> >> - any x.y.z release only introduces bugfixes. These releases are done >> every four weeks, like clockwork. If a fix doesn't make

Re: A new release process?

On 12/29/2016 08:16 PM, David Zuelke wrote: The tl;dr of this approach is that - any x.y.z release only introduces bugfixes. These releases are done every four weeks, like clockwork. If a fix doesn't make the cut for a release, it'll end up in the next one; - x.y.0 releases, on the other hand,

Re: A new release process?

On Thu, Dec 29, 2016 at 11:16 PM, David Zuelke wrote: > As a, more or less, "outside observer", I happen to think that the current > method of voting on finals, instead of a practice of rolling out RCs (that > are then left up for testing for at least a week), is fundamentally

A new release process?

Hi everyone, Given the several current threads where there's arguing about what and how and when to release features, backported or not, I'd like to offer a tale of a project that was, more or less, in the same dire spot, and pulled itself out of that misery with great success and universal