Re: 0.7 Priorities

2012-02-22 Thread Jeff Eastman
Sure, just look at Hadoop. But I'm not hung up on the port/starboard numbering scheme either. Either 0.6.1 or 0.7 work for me. On 2/22/12 11:46 AM, Jake Mannix wrote: On Wed, Feb 22, 2012 at 10:40 AM, Dmitriy Lyubimovwrote: I guess i still prefer 0.6.1 for maintenance releases (esp. given the

Re: 0.7 Priorities

2012-02-22 Thread Dmitriy Lyubimov
ok, sounds good. i am not fixated on names. On Wed, Feb 22, 2012 at 10:46 AM, Jake Mannix wrote: > On Wed, Feb 22, 2012 at 10:40 AM, Dmitriy Lyubimov wrote: > >> I guess i still prefer 0.6.1 for maintenance releases (esp. given the >> short cycle). >> >> Another supporting argument against even/o

Re: 0.7 Priorities

2012-02-22 Thread Jake Mannix
On Wed, Feb 22, 2012 at 10:40 AM, Dmitriy Lyubimov wrote: > I guess i still prefer 0.6.1 for maintenance releases (esp. given the > short cycle). > > Another supporting argument against even/odd scheme is that this > naming doesn't really reflect the actual level of product maturity > (e.g. 1.0 th

Re: 0.7 Priorities

2012-02-22 Thread Dmitriy Lyubimov
I guess i still prefer 0.6.1 for maintenance releases (esp. given the short cycle). Another supporting argument against even/odd scheme is that this naming doesn't really reflect the actual level of product maturity (e.g. 1.0 this way ends being a "new-feature-being-unstable-beta"? whereas in real

Re: 0.7 Priorities

2012-02-22 Thread Geek Gamer
Odd / Even releases for cleanup maintenance vs feature additions looks great. On Wed, Feb 22, 2012 at 8:58 PM, John Conwell wrote: > I think it sounds like a good idea. > > On Wed, Feb 22, 2012 at 4:24 AM, Jake Mannix wrote: > >> On recent threads on the dev@ list, and discussions off-list, it's

Re: 0.7 Priorities

2012-02-22 Thread John Conwell
I think it sounds like a good idea. On Wed, Feb 22, 2012 at 4:24 AM, Jake Mannix wrote: > On recent threads on the dev@ list, and discussions off-list, it's pretty > clear that we need to have "cleanup" be a priority for the next release. > > How about this for a formal proposal: > > > - The

Re: 0.7 Priorities

2012-02-22 Thread Ted Dunning
Aye say I. Sent from my iPhone On Feb 22, 2012, at 4:24 AM, Jake Mannix wrote: > > If we're able to wrap this release up cleanly and get quickly moving on to > new features again, maybe we can try this on a more regular basis, with > even releases being feature-work, and odd releases being ma

Re: 0.7 Priorities

2012-02-22 Thread Grant Ingersoll
On Feb 22, 2012, at 7:24 AM, Jake Mannix wrote: > On recent threads on the dev@ list, and discussions off-list, it's pretty > clear that we need to have "cleanup" be a priority for the next release. > > How about this for a formal proposal: > > > - The 0.7 release will have issues (both ne

0.7 Priorities

2012-02-22 Thread Jake Mannix
On recent threads on the dev@ list, and discussions off-list, it's pretty clear that we need to have "cleanup" be a priority for the next release. How about this for a formal proposal: - The 0.7 release will have issues (both new and on JIRA) be primarily focused on bugfixes / cleanup /