I believe from comments on the mailing list that Rev 4.0 is used. I also believe that it is stable enough that people are not entering bugs, as such. I only believe the trunk should be use as a release, like in the nightly builds, once the testing and verification of every commit is done. i do believe that is what is suppose to happen now from what I read about committing. However I see signs from the commit logs of things being entered and then corrected. This indicates to me that testing is not done before commits.
David E Jones sent the following on 11/13/2008 10:45 PM: > > On Nov 12, 2008, at 12:04 PM, Adrian Crum wrote: > >> David E Jones wrote: >>> - Framework release >>> - gather ideas from people in a confluence page (TODO: add my own) >>> - complex UIs, GWT, DOJO, etc renderers for widgets >> >> I've been thinking about the framework release and our current Release >> 4. Release 4 will be two years old in a few months. A lot has been >> done to the project since the R4 branch. How about making a Release 5 >> branch (whole project) sometime around Spring? > > I think that's fine. Hopefully by then we'll have more framework things > done. > > What I'd really like to hear for releases is what people plan to do with > the release branch. In general in order to facilitate collaboration and > such it is best to use the trunk. Unless we have a lot of people using > OFBiz OOTB then it may not make sense to do releases at all, even "lite" > releases like these release branches. > > Still, we can and should do them periodically, and they are of course > very easy to do (just make a branch...) and then it is up to individuals > to decide whether to use it and fix bugs in it or now. > > >> I don't mean to dilute the framework release effort. But at the same >> time, it seems to me issues are coming up in R4 that have been >> addressed in the trunk. > > While to some extent this depends on the type of issue, in general > issues in the 4.0.0 branch should be fixed in that branch by the > "sub-community" that has formed around the branch. If things are not > getting fixed, to me that means the branch has not attracted enough of a > user and contributor community. I don't know how to fix that problem... > > -David > > > > >
