+/-0 for giving site "tags", "branches", and "trunk". It might be nice to have the site built from site/tags/PRODUCTION so we could have some sort of a release cycle for the site, but (OTOH) it might be nice to keep it simple and just have content under site.
Anyone? Tim > -----Original Message----- > From: Henri Yandell [mailto:[EMAIL PROTECTED] > Sent: Saturday, November 27, 2004 11:56 AM > To: Jakarta Commons Developers List; Martin Cooper > Subject: Re: Volunteer for SVN migration management? Was: > Migrate to SVN? > > From a Jakarta level view, I really want to push for: > > jakarta/<subproject>/<whatever...> > > Other than that, I'll work with anything :) > > (Which I just noticed Velocity haven't done, so will see if I > can get them to change). > > On Fri, 26 Nov 2004 21:52:22 -0800, Martin Cooper > <[EMAIL PROTECTED]> wrote: > > On Sat, 27 Nov 2004 00:35:14 -0500, Tim O'Brien > <[EMAIL PROTECTED]> wrote: > > > Martin, > > > > > > I'm available if you need help. > > > > Thanks, I appreciate that. > > > > > One thing to flesh out is structure - here are some proposals: > > > > Summarising my preferred versions of your alternatives, we > might have: > > > > jakarta/ > > commons/ > > proper/ > > ... > > digester/ > > branches/ > > tags/ > > trunk/ > > ... > > site/ > > branches/ > > tags/ > > trunk/ > > sandbox/ > > ... > > bzip2/ > > branches/ > > tags/ > > trunk/ > > ... > > > > This gives each component its own branches and tags, which > makes more > > sense to me than having Commons-wide tagging and branching. As > > mentioned, it also makes 'site' its own thing, rather than > pretending > > that it's a component. > > > > Comments? > > > > -- > > Martin Cooper > > > > > > > > > > > Commons Proper Components > > > > > > 1. /jakarta/commons/digester/[tags|branches|trunk] > > > 2. /jakarta/commons/proper/digester/[tags|branches|trunk] > > > > > > Commons Sandbox Components (just using bzip2 because it is there) > > > > > > 1. /jakarta/commons-sandbox/bzip2/[tags|branches|trunk] > > > 2. /jakarta/commons/sandbox/bzip2/[tags|branches|trunk] > > > > > > Anybody have other options? > > > > > > I look at the existing velocity project, and part of me > just wishes > > > they had combined all velocity related "modules" under a > velocity directory. > > > If everything "commons" where under a commons directory, then we > > > could have a separate directory for the commons site - something > > > like /jakarta/commons/site. "site" would then not be a > sibling to a > > > real project. > > > > > > Tim "2 cents" O'Brien > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: Martin Cooper [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, November 26, 2004 11:11 PM > > > > To: Jakarta Commons Developers List; Henri Yandell > > > > Subject: Re: Volunteer for SVN migration management? > Was: Migrate > > > > to > > > SVN? > > > > > > > > On Fri, 26 Nov 2004 13:31:27 -0500, Henri Yandell > > > > <[EMAIL PROTECTED]> > > > > wrote: > > > > > Do we have a volunteer to organise the move of Commons to SVN? > > > > > > > > Sure, I'll step up, unless someone else has a strong > desire to do it. > > > > > > > > > (which is probably some combination of: vote, plan, > liaise with > > > infra) > > > > > > > > Yep, I expect I'll be doing all three at once. ;-) > > > > > > > > -- > > > > Martin Cooper > > > > > > > > > > > > > Hen > > > > > > > > > > On Fri, 26 Nov 2004 10:54:37 -0500, Phil Steitz > > > > > <[EMAIL PROTECTED]> > > > wrote: > > > > > > +1 from me as well -- seems to make sense to move > as a group. > > > > > > > > > > > > Phil > > > > > > > > > > > > > > > > > > > > > > > > Alex Karasulu wrote: > > > > > > > +1 > > > > > > > > > > > > > > Noel J. Bergman wrote: > > > > > > > > > > > > > >>>> 6) should I just delete the > > > > > > >>>> /jakarta-commons-sandbox/email directory, or leave the > > > > > > >>>> folder and a note pointing to the promotion? What > > > > about the > > > > > > >>>> website as well? I think for [configuration] we just > > > > > > >>>> deleted > > > > both. > > > > > > >>>> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >>> The ideal scenario would be to use "cvs delete" > on all the > > > sandbox > > > > > > >>> files, so that the original history is > maintained there, > > > > > > >>> but > > > > nobody > > > > > > >>> who checks out the sandbox (with "-dP" at least) will be > > > bothered > > > > by > > > > > > >>> the files. > > > > > > >>> > > > > > > >> > > > > > > >> > > > > > > >> The IDEAL situation would be to convert Jakarta > Commons to SVN. > > > > Can we > > > > > > >> PLEASE consider doing so? > > > > > > >> > > > > > > >> A lot of projects, including the HTTP Server > project, have > > > > > > >> been migrating, as can be seen from > > > > > > >> http://svn.apache.org/viewcvs. Jakarta and > > > XML > > > > are > > > > > > >> definitely the laggards now. > > > > > > >> > > > > > > >> --- Noel > > > > > > >> > > > > > > >> > > > > > > >> > > > > ------------------------------------------------------------------- > > > > -- > > > > > > >> To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > > > >> For additional commands, e-mail: commons-dev- > > > > [EMAIL PROTECTED] > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > - > > > > > > > To unsubscribe, e-mail: > > > [EMAIL PROTECTED] > > > > > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > > > > To unsubscribe, e-mail: > > > > > > [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > > > To unsubscribe, e-mail: > > > > > [EMAIL PROTECTED] > > > > > For additional commands, e-mail: > > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > --- > > > > > > > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > > > > [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
