Re: [jdee-devel] Subversion updates
Brought to you by:
paullandes
From: Paul L. <la...@ma...> - 2009-05-14 05:27:41
|
No, the 2.3.6 branch is done. There will be no more development on it. New development is now done on 2.4. If we do development on the trunk and mess it up, others will download and won't be able to compile. Once we get a release candidate for 2.4, we'll replace trunk with it. The idea is trunk has something stable for users. Len Trigg writes: > Paul Landes wrote: > > - trunk/* has moved to tags/jde-2.3.5-devel. Any work here needs to be added > > to the 2.4 branch. > > - branches/2.3.6 has been renamed to branches/2.3.6-rc to carry forward the > > release candidate convention > > - branches/2.3.6-rc has been copied to trunk > > - branches/2.3.6-rc has been copied to branches/2.4, which is currently the > > UN-stable development branch for which all outstanding patches and current > > development is applied. > > I'm a little confused by this -- the outcome seems like there will be > three places where ongoing development could occur: > > trunk > branches/2.3.6-rc (or branches/2.3.6 as suggested by Phillip/Ian) > branches/2.4 > > Since the next release is presumably from the 2.3.6 branch, a 2.4 > release is probably a ways away, so development toward 2.4 may as well > occur on the trunk. Creation of branches/2.4 isn't actually needed > until a 2.4 release is imminent enough that you need a separation of > "unstable development" from "polish to 2.4" to occur. > > > > Also, I've thought about moving everything to GIT (again by suggestion by > > Ian). Thoughts? > > I agree with the general sentiment to get a couple of releases out > first. > > > Cheers, > Len. -- Paul Landes la...@ma... |