I agree. I think we should take the approach that the next version will be a patch release, not a minor version and only change to a minor version if required. IOW, the current pom.xml files should all specify 2.0.1-SNAPSHOT as the version instead of 2.1-SNAPSHOT. This isn’t a big deal as it can be fixed during the release but it would be nice if the SNAPSHOT version always reflected what the next release is actually going to be.
Ralph On Jul 16, 2014, at 8:14 AM, Gary Gregory <[email protected]> wrote: > Now that 2.0 is done, I think it would be nice to see a 2.0.1 as soon as we > resolve the last of the Android issue from the current batch. > > We can advertise 2.0.1 as the "Android" release which also include whatever > tidbits (better status logger) have made it into trunk. > > I suggest this now while Ralph still has his RM hat on and we have a user > that has been quite helpful on testing Android patches. And we are also all > till in the releasing mindset and are paying attention. For 2.1, we can take > a breath, and regroup. > > Thoughts? > > Gary > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
