Without the flow logging API changes and gc-free stuff it would just be a 2.5.1 release, no?
On Sun, Feb 21, 2016 at 5:02 PM, Gary Gregory <[email protected]> wrote: > FWIW: From a practical POV, one way to do this would be to branch master > into a 2.6 branch and prune the branch of the new stuff. > > Gary > > On Sat, Feb 20, 2016 at 10:22 PM, Gary Gregory <[email protected]> > wrote: > >> Hi All: >> >> Since we have a nice stack of changes already, I would like for us to >> consider the following: >> >> Release 2.6 without the new flow tracing APIs and without the new >> low/no-GC code (ByteBufferDestination and all). >> >> Then we can make the next release have two themes: flow tracing and >> no/low GC. >> >> This would avoid too big a 2.6 release in relation to 2.5. >> >> Thoughts? >> >> Gary >> >> -- >> E-Mail: [email protected] | [email protected] >> Java Persistence with Hibernate, Second Edition >> <http://www.manning.com/bauer3/> >> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> >> Spring Batch in Action <http://www.manning.com/templier/> >> Blog: http://garygregory.wordpress.com >> Home: http://garygregory.com/ >> Tweet! http://twitter.com/GaryGregory >> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
