I read the SVN branching doc on the wiki, and here is some feedback. Instead of putting branches tags directories at the repository level where "/prod", "/qa", and "/trunk" encompass everything in the SVn repository. Create "trunk", "tags", and "branches" at the subproject level. Version each subproject in a /projects subdirectory and aggregate projects using svn:externals. It's convenient to keep all of the tags and branches of a specific component in a consolidated directory as I'm almost certain that there are SVN tools in development which will expect the familiar trunk, tags, branches convention.
Thinking of a branch or a tag as something that happens to an entire repository is in keeping with the way JBoss performs releases in CVS. From what I heard last year, when JBoss cuts a release or tags, someone has to tag (or branch tag) the entire JBoss CVS repository. The drawback to repository-wide branching and tagging is that it prevents different subcomponents from releasing at different rates. Hibernate, jboss-mail, jboss-media, jboss-aop...all of these components may have different release rates. From the wiki document, it looks like every project that follows the three-tiered release model would have a directory in /trunk, /qa, and /prod. I'm assuming that the idea of putting /trunk, /qa, and /prod is one of convenience? This way someone only has to check out /trunk to get all trunks? If that's the motivation, then you could handle this case by using svn:externals and preserve the convention of "trunk", "tags", and "branches". Put trunk, "tags", and "branches" at the second level (keep the names as certian toolsets will start relying on this convention). Resources on trunks, tags, branches: "Subversion Book" - http://svnbook.red-bean.com/en/1.1/ch05s04.html "How Fisheye works with Trunks, Tags, Branches" - http://www.cenqua.com/fisheye/doc/1.1/admin/svnsymbolic.html Note: I'd suggest either the second-level approach or a custom layout. Other projects have had similar discussions: http://lists.gnu.org/archive/html/gnustep-dev/2005-10/msg00057.html http://pkg-perl.alioth.debian.org/subversion.html --- Adrian Brock <[EMAIL PROTECTED]> wrote: > I thought the plan was to validate first? > > We can't just make a switch to SVN at 5 minutes notice > on a few peoples' say so. > > People need to confirm they can switch to the new tools > and have time to adapt. e.g. > > * they already have unchecked in work against cvs > * they need to download and understand the tools > * they need to find and discuss problems > > I used SVN for the first time only yesterday. :-) > > I found checking out from SVN and performing the maven build very slow > compared to what we have now. > Admittedly it will be faster now I have a populated local repository. > > I still don't know how to make this compile within Eclipse? > i.e. > Without a standard location for thirdparty how do we share the > Eclipse project descriptors? > Although, I believe Maven has a task to generate them locally > rather than sharing them, I don't currently know how to do this. > > On Sat, 2006-02-11 at 16:03, Scott M Stark wrote: > > 4.0 vs head is a tradeoff of how long its going to take and how this > > relates to how much has to be merged to the ultimate svn structure. > > > > What are you referring to in terms of increased time, the download from > > the repository, maven, both? > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > > Andrew Oliver > > Sent: Saturday, February 11, 2006 12:47 PM > > To: jboss-development@lists.sourceforge.net > > Subject: Re: Ongoing build changes: was RE: [JBoss-dev] > > OntheedgeoftheMavencliff > > > > gosh wouldn't it make more sense to do all of this for 5.0 where there > > is a free hand rather than 4.0? > > > > Do we have feasibility targets (i.e. the build cannot suddenly take 5 > > hours on a IA64 with 8 gb of ram) for this? > > > > -andy (who finds maven and all things like it to be really frustrating) > > > > Damon Sicore wrote: > > > Adding them now... ;-) > > > > > > On Feb 11, 2006, at 2:38 PM, Scott M Stark wrote: > > > > > >> That would be a way to actually start with a 4.0 branch fork which > > might > > >> be more manageable due to fewer changes to merge between the cvs and > > svn > > >> repositories. > > >> > > >> Can we get the jboss-4.0.x and jboss-head contents moved into svn > > Damon? > > >> > > >> -----Original Message----- > > >> From: Adrian Brock > > >> Sent: Saturday, February 11, 2006 3:48 AM > > >> To: Scott M Stark > > >> Cc: jboss-development@lists.sourceforge.net; QA > > >> Subject: RE: Ongoing build changes: was RE: [JBoss-dev] > > >> OntheedgeoftheMavencliff > > >> > > >> On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: > > >> > > >>> On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: > > >>> > > >>>> Let's do that. Do you want to couple this to maven? It would help > > >> > > >> Ruel I > > >> > > >>>> suppose. > > >>> > > >>> > > >>> We may as well go "Big Bang!". :-) > > >> > > >> > > >> Speaking of Big Bang. It might be idea to convert to subversion at > > the > > >> same time. > > >> Given we want to refactor the project structures to native Maven > > >> we could: > > >> > > >> 1) Import CVS into SVN > > >> 2) Use SVN rename to rework the project structure > > >> 3) Keep the history attached to those files! > > >> > > >> http://weblogs.java.net/blog/joshy/archive/2005/03/ > > subversion_rena.html > > >> -- > > >> xxxxxxxxxxxxxxxxxxxxxxxx > > >> Adrian Brock > > >> Chief Scientist > > >> JBoss Inc. > > >> xxxxxxxxxxxxxxxxxxxxxxxx > > >> > > >> > > >> > > >> ------------------------------------------------------- > > >> This SF.net email is sponsored by: Splunk Inc. Do you grep through > > >> log files > > >> for problems? Stop! Download the new AJAX search engine that makes > > >> searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > > >> _______________________________________________ > > >> JBoss-Development mailing list > > >> JBoss-Development@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > > > > files > > > for problems? Stop! Download the new AJAX search engine that makes > > > searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > > http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 > > > _______________________________________________ > > > JBoss-Development mailing list > > > JBoss-Development@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > > _______________________________________________ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 > > _______________________________________________ > > JBoss-Development mailing list > > JBoss-Development@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/jboss-development > -- > xxxxxxxxxxxxxxxxxxxxxxxx > Adrian Brock > Chief Scientist > JBoss Inc. > xxxxxxxxxxxxxxxxxxxxxxxx > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
