10:01 a.m.
And here is the list of issues scheduled for this release: http://goo.gl/45Osp
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
1:23 p.m.
I'm puzzled by the pace.
We just forked from 5.3, we get no time to do all the refactoring and
API changes we had in mind?
-1 to do those after the Alpha1 tag
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.
On 4 July 2013 09:01, Mircea Markus <mmarkus(a)redhat.com> wrote:
And here is the list of issues scheduled for this release:
http://goo.gl/45Osp
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
12:25 a.m.
On 4 Jul 2013, at 14:23, Sanne Grinovero <sanne(a)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)
12:31 p.m.
On 4 July 2013 23:25, Mircea Markus <mmarkus(a)redhat.com> wrote:
On 4 Jul 2013, at 14:23, Sanne Grinovero <sanne(a)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).
Sorry I'm just not used to this approach. It might be my own habits, I
would generally consider it way too short but have no specific
problems with it. All cool things we planned where moved out anyway..
I just hope we'll not have to wait too long for some of those.
Sanne
> 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)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
1:09 p.m.
On 5 Jul 2013, at 12:31, Sanne Grinovero <sanne(a)infinispan.org> wrote:
On 4 July 2013 23:25, Mircea Markus <mmarkus(a)redhat.com>
wrote:
> On 4 Jul 2013, at 14:23, Sanne Grinovero <sanne(a)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).
Sorry I'm just not used to this approach. It might be my own habits, I
would generally consider it way too short but have no specific
problems with it.
Hmm, we've been developing things for almost one month and we
have what to give community to test, I'm puzzled why you consider this a short time
for a release :-)
All cool things we planned where moved out anyway..
Which features exactly?
I just hope we'll not have to wait too long for some of those.
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
3970
days inactive
3971
days old
infinispan-dev@lists.jboss.org
4 comments
2 participants
participants (2)
-
Mircea Markus -
Sanne Grinovero