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 <ttarr...@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@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
