Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread Jonathan Haddad
+1 as well On Mon, Nov 21, 2016 at 10:59 AM kurt Greaves wrote: > yep +1 to this. The LTS release solves my previous concern >

Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread kurt Greaves
yep +1 to this. The LTS release solves my previous concern

Re: Proposals for releases - 4.0 and beyond

2016-11-21 Thread Blake Eggleston
I really like Stefan's Ubuntu model (because of the LTS release), with Sylvain's suggestion a close second. Both because I think we should do a supported, non-dev release every 6 months, and release bug fixes for them for a at least a year. On November 19, 2016 at 10:30:02 AM, Stefan

Re: Proposals for releases - 4.0 and beyond

2016-11-20 Thread Mick Semb Wever
On 19 November 2016 at 10:49, Jeff Jirsa wrote: > Option #3: Sylvain proposed [3] feature / testing / stable branches, Y > cadence for releases, X month rotation from feature -> testing -> stable -> > EOL (X to be determined). This is similar to an Ubuntu/Debian like

Re: Proposals for releases - 4.0 and beyond

2016-11-19 Thread Stefan Podkowinski
I’d like to suggest an option similar to what Jeremiah described and that would basically follow the Ubuntu LTS release model [1], but with shorter time periods. The idea would be to do a stable release every 6 months with 1 year bug fixing support. At the same time, every third stable release

Re: Proposals for releases - 4.0 and beyond

2016-11-19 Thread Samuel CARRIERE
: Re: Proposals for releases - 4.0 and beyond Option 3 seems the most reasonable and the clearest from a user perspective. The main thing I'd be concerned about with a 6 month cycle would be how short a branch is supported for. Most users will be bound to a specific release for at least 2 yea

Re: Proposals for releases - 4.0 and beyond

2016-11-18 Thread kurt Greaves
Option 3 seems the most reasonable and the clearest from a user perspective. The main thing I'd be concerned about with a 6 month cycle would be how short a branch is supported for. Most users will be bound to a specific release for at least 2 years, and we still find bugs in 2.1 2 years since

Re: Proposals for releases - 4.0 and beyond

2016-11-18 Thread Jeremiah D Jordan
I think the monthly releases are important, otherwise releases become an “event”. The monthly releases mean they are just a normal thing that happens. So I like any of 3/4/5. Sylvain's proposal sounds interesting to me. My only concern would be with making sure we label things very clearly

Proposals for releases - 4.0 and beyond

2016-11-18 Thread Jeff Jirsa
With 3.10 voting in progress (take 3), 3.11 in December/January (probably?), we should solidify the plan for 4.0. I went through the archives and found a number of proposals. We (PMC) also had a very brief chat in private to make sure we hadn’t missed any, and here are the proposals that we’ve