Mmm... I did not thought about that... To ease reflexion/discussion a quote :
"Release branches will be created approximately once per year; these will represent a new minor version number, and in cases of major and/or non-backward compatible changes a major version number" We may use the same acronym than Ubuntu (LTS or our own brand ;o) to characterize major and/or non-backward compatible changes in branches names ? Jacques ----- Original Message ----- From: "David E. Jones" <[EMAIL PROTECTED]> To: <dev@ofbiz.apache.org> Sent: Saturday, January 13, 2007 9:22 PM Subject: Re: Board Report Draft - Please Review ASAP > > If there is enough interest in it then we should certainly go for it, > or at least consider it. > > The main reason I don't like it is because it doesn't represent the > proposed branching process very well. > > -David > > > On Jan 13, 2007, at 10:27 AM, Jacques Le Roux wrote: > > > This was only a suggestion, I like it because with this you have > > more information than just a number. But I will not push more for > > this... > > > > Jacques > > > > ----- Original Message ----- > > From: "David E. Jones" <[EMAIL PROTECTED]> > > To: <dev@ofbiz.apache.org> > > Sent: Saturday, January 13, 2007 5:13 PM > > Subject: Re: Board Report Draft - Please Review ASAP > > > > > >> > >> On Jan 13, 2007, at 4:15 AM, Jacques Le Roux wrote: > >> > >>> BTW David, I put a comment as answer to your question about > >>> release in > >>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan? > >>> focusedCommentId=1027#comment-1027 > >> > >> Yeah, this sort of thing should probably be discussed on the mailing > >> list and then once discussed we can decide if any change to the > >> document needs to be done. > >> > >> I'm not so sure about the Ubuntu versioning mechanism... I think it > >> is much more clear if each branch we do is represented by a major/ > >> minor version number change, and then follow on releases within that > >> branch would be represented by the sub-minor version number change. > >> > >> Anyway, this is described in the General Release Policies. > >> > >> Are you saying that you propose to do this differently? > >> > >> -David > >> > >> > >> > > > >