[infinispan-dev] Infinispan 7.0 feature freeze and future planning

Tristan Tarrant ttarrant at redhat.com
Fri Sep 26 04:18:04 EDT 2014

Obviously this is not a hard freeze: 7.0.0.Final is still a month away, 
so there is time to refine things that are already in there.

To bring a couple of examples:

ISPN-4753 Add oldValue, oldMetadata and retry flag to filter and 
converter for Cluster Listeners
This one is obviously a feature refinement, and essential to have in 7.0.

ISPN-4752 Implement native getAll/putAll operations in Hot Rod 2.0
This one introduces a modification to the HotRod protocol (probably 
2.1), but it can safely be pushed to 7.1, since it is augmentative.

In essence, I trust everybody's common sense to focus on the essentials 
to avoid further meandering :)


On 26/09/14 10:02, Emmanuel Bernard wrote:
> Not so theoretical question.
> What about features that are being refined (like clustered / remote listener as seen int he recent days).
> Are these improvements to be removed under the feature freeze hammer. That would possibly impact our ability  to do them in 7.x if APIs change.
> Or are they part of the maturation cycle after feature freezing?
>> On 25 sept. 2014, at 17:31, Tristan Tarrant <ttarrant at redhat.com> wrote:
>> Hi all,
>> Infinispan 7.0 has been in development for over 9 months now and we
>> really need to release it into the wild since it contains a lot of juicy
>> stuff :)
>> For this reason I'm calling a feature freeze and all new features need
>> to be reassigned over to 7.1 or 7.2.
>> For the next minor releases I would like to suggest the following strategy:
>> - use a 3 month timebox where we strive to maintain master in an "always
>> releasable" state
>> - complex feature work will need to happen onto dedicated feature
>> branches, using the usual GitHub pull-request workflow
>> - only when a feature is complete (code, tests, docs, reviewed,
>> CI-checked) it will be merged back into master
>> - if a feature is running late it will be postponed to the following
>> minor release so as not to hinder other development
>> Suggestions, amendments to the above are welcome.
>> Thanks !
>> Tristan
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

More information about the infinispan-dev mailing list