one clarification, when I say plan, it is not a detailed requirement etc, just some features that we thought would be better to be included, but if it turns out can not be completed in the given time frame, we can delay it to next release for sure.
Regards Jeff On Fri, Jun 18, 2010 at 7:51 PM, Jeff Yu <jeff.yuch...@gmail.com> wrote: > I think this can come from our long-term goal, we can have this sort of > discussion just after the release. > IMHO, Certainly, for the bug fix release, we can just grab what we have and > deliver. > but for others, it is better that we have some plans. > > Regards > Jeff > > > On Fri, Jun 18, 2010 at 7:40 PM, Rafal Rusin <ra...@intalio.com> wrote: > >> And one thing. I don't like planning for particular features to >> include in some release. I prefer to grab what we have in regular >> period of time and make release from it (and move outstanding issues >> into next release). This is how it works. >> >> On Fri, Jun 18, 2010 at 11:35 AM, Rafal Rusin <ra...@intalio.com> wrote: >> > On Fri, Jun 18, 2010 at 11:19 AM, Tammo van Lessen < >> tvanles...@gmail.com> wrote: >> >> Hi, >> >> >> >> I'm fine with that, too. We should also define a long-term road map. >> >> >> >> Regarding the versions, especially when we release more often (which I >> >> would really appreciate), we should better communicate the philosophy >> >> behind versioning. 1.3.x should never require migration efforts and >> >> should be considered drop-in replacements for 1.3.(x-1), as long as bug >> >> fixes allow this. Once migration is necessary, we should increase the >> >> minor version. So the JPA changeset should go into 1.4 then. >> > >> > Right, we should obey those 3 digits versioning rules >> > (http://en.wikipedia.org/wiki/Software_versioning). >> > We'll start this from 1.4. >> > >> >> >> >> The question would be if we need a 1.3.5 or if we can go directly for a >> 1.4. >> > >> > We can now stay with 1.3.5. If JPA refatoring will be committed before >> > 15-th July, then we'll mark it 1.4. >> > Otherwise we'll stay with 1.3.5. >> > >> >> >> >> Tammo >> >> >> >> On 18.06.2010 10:54, Rafal Rusin wrote: >> >>> 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 <jef...@apache.org> 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 >> >>>> >> >>> >> >> >> >> -- >> >> Tammo van Lessen - http://www.taval.de >> >> >> > >> > >> > >> > -- >> > Regards, >> > Rafał Rusin >> > http://rrusin.blogspot.com >> > >> >> >> >> -- >> Regards, >> Rafał Rusin >> http://rrusin.blogspot.com >> > > > > -- > Cheers, > Jeff Yu > > ---------------- > blog: http://jeff.familyyu.net > > -- Cheers, Jeff Yu ---------------- blog: http://jeff.familyyu.net
