The effort required to officially release 1.5.2 could probably be better spent elsewhere. As long as the 1.5.x branch is kept, users would still be free to get and build from source if they wanted.
I imagine that the benefits in 2.0 would drive the majority of users to bite the bullet and upgrade anyway, especially if 1.5.2 isn't merely a drop in replacement for 1.5.1. As long as we provide adequate upgrade documentation ( https://issues.apache.org/jira/browse/PIVOT-643) then I think focusing on 2.0 is preferable. Chris On 24 September 2010 18:58, Greg Brown <[email protected]> wrote: > Hi all, > > I'd like to start the process of getting Pivot 2.0 ready for release. There > are still 25 open issues in JIRA, but a number of them should be pretty easy > to resolve and the rest can be pushed to a maintenance release or Pivot 2.1. > > Pivot 2.0 represents a huge step forward in many respects, and I'd like to > get it in front of developers as soon as possible. If you could try to wrap > up any features or issues you have been working on over the next few weeks, > that would be great. In the meantime, I plan to start testing and updating > documentation. It would be great if we could get 2.0 out the door by the end > of October or mid-November at the latest. Once we get into December, it is > harder to make a splash with a release announcement. > > We also have a number of changes in the pipeline for 1.5.2. I had > originally assumed that we would release 1.5.2 well before 2.0 - now that > 2.0 is close to release, I'm not sure we should bother. 1.5.2 does have some > useful fixes and improvements, but it also has a few breaking API changes > (something we had originally hoped to avoid for maintenance releases). All > of these changes have also been incorporated into 2.0 - since we'd probably > recommend that most developers upgrade to 2.0 anyways, should we still > release 1.5.2 as well? > > Please let me know what you think. > > Thanks, > Greg > >
