yes, move to SVN as it is and restructure then.
also gives us additional time to consider all necessary refactorings  ;-) 
-M

On 4/13/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> +1
> 
> Manfred, are we talking about moving to SVN *before* restructuring?
> If so that makes sense.  The move should be made easier b/c we have no
> branches (just one we made for tree2 but never used.)  Also, James
> Mitchell has offered to help advise us on the move (he is familiar
> with SVN from his work on Struts.)
> 
> On 4/13/05, Heath Borders <[EMAIL PROTECTED]> wrote:
> > +1.  I've been using it on WSAD w/o integrated support for about a year now,
> > and its really not that painful.
> >
> >
> >
> > On 4/13/05, David Heffelfinger <[EMAIL PROTECTED]> wrote:
> > > +1
> > >
> > > I'm not sure if non committers are allowed to vote, count it if we are,
> > > feel free to ignore if we are not.
> > >
> > > David
> > >
> > >
> > >
> > > On 4/13/05, Sylvain Vieujot <[EMAIL PROTECTED] > wrote:
> > > > +1
> > > >
> > > >
> > > > On Wed, 2005-04-13 at 10:19 +0200, Manfred Geiler wrote:
> > > > Final release 1.0.9beta is only a question of hours now. After
> > > > publication will be the best time to finally move our repository out
> > > >
> > > >
> > > > of the incubator.
> > > > We have already discussed and voted about the SVN issue, but there are
> > > > some new and changed circumstances and I would like to find out if
> > > >
> > > >
> > > > there are still committers who have serious objection against SVN.
> > > > Cons:
> > > > - IntelliJ users still do not have integrated SVN support.
> > > >
> > > > Pros:
> > > > - SVN is the new repository technology for ASF. At the long term all
> > > > Apache projects should have moved to SVN. So it's unwritten common
> > > >
> > > > sense that new top level projects should start with SVN from the
> > > > beginning.
> > > > - As you know, SVN is able to keep history for renamed and moved files
> > > >
> > > > and dirs. Just now we are discussing some serious structural changes
> > > > (subprojects, sandbox, etc.) If we do that now in CVS we would loose
> > > >
> > > >
> > > > valuable history for many files.
> > > > - TortoiseSVN is a powerful alternative for all IntelliJ users in the
> > meantime.
> > > >
> > > > So here is my definite
> > > >
> > > >
> > > > +1 for switching from CVS to Subversion
> > > >
> > > > -Manfred
> > > >
> > > >
> > >
> > >
> >
> >
> >
> > --
> > -Heath Borders-Wing
> > [EMAIL PROTECTED]
>

Reply via email to