[infinispan-dev] 6.0.0.Alpha1 scheduled for 12th July (Friday)

[Mircea Markus]

On 4 Jul 2013, at 14:23, Sanne Grinovero <sanne at infinispan.org> wrote:

> I'm puzzled by the pace.
> We just forked from 5.3,

Just forked ? :-)
By the time we release Alpha1 (12 July), the 6.0 branch will be running for almost one month on its own branch (cut in 17 Jul). Also the work of 6.0 features has been started way before the actual tagging took place (e.g. remote querying). 

> we get no time to do all the refactoring and
> API changes we had in mind?

Why do we need to release all the refactoring in the first alpha? There are three Alphas(https://issues.jboss.org/secure/Dashboard.jspa?selectPageId=12315590) scheduled for 6.0 in which we'll have time to incrementally add more API changes. 

> 
> -1 to do those after the Alpha1 tag

why?
Alpha don't require API freezes. OTOH we have some features that can be released to the community already: 
https://issues.jboss.org/browse/ISPN-3109
https://issues.jboss.org/browse/ISPN-2861
https://issues.jboss.org/browse/ISPN-761

Bear in mind that we are targeting 3-4 months release cycles for a Final, so we should keep releasing every 2 weeks or so (preferably shorter release cycles).

> 
> Also we had discussed to base 6.0 on newer Hibernate Search 5.0, but
> we barely started that work. With this pace it means we'll switch to
> Search 5.0 (and new API) in a late phase of Infinispan 6.0 releases.

Again I don't see how these are related. There are more alphas on the way in which we can tackle that.

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)