I would prefer to release 1.3.5 and then 1.4.0. I'm fine with 1.3.5 as soon as there are running maven axis2-war tests in hudson.
And I agree - we should release regularly. Something like every 2 months with 1 month forking period (beta release). So we can plan 1.3.5 fork on 15-th July and release on 15-th August (along with 1.4 fork). On Fri, Jun 18, 2010 at 6:00 AM, Jeff Yu <[email protected]> wrote: > Hi team, > > Since we've released the 1.3.4, I am thinking about our roadmap for the next > release. > > Firstly, I'd think that it is better that we have a release plan like 1 > release in 2 months at least, could be just a bug fix release, or a feature > enhancement, as long as we have something to deliver, > don't want us to be in the position that have 1 release in 6 months. ;), > what do you think of this? we should create a wiki page to state whats the > tentative release date for our next release, and whats the feature or it is > just a bug fix release over there. > > Secondly, as we discussed on the other thread with regard to the jpa > refactoring table renaming, we thought it is better that we did this on 1.4 > release, as for 1.3.x series, we shouldn't expect to have big impact on the > database schema change, > in this case, would be for the OpenJPA users. > > So here is the question, what is our next release? 1.3.5 or 1.4? > > Let me know what do you think of this. > > -- > Cheers, > Jeff Yu > > ---------------- > blog: http://jeff.familyyu.net > -- Regards, Rafał Rusin http://rrusin.blogspot.com
