Return-Path: 
 <commons-dev-return-63257-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 22534 invoked from network); 27 Nov 2004 05:24:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 27 Nov 2004 05:24:32 -0000
Received: (qmail 16494 invoked by uid 500); 27 Nov 2004 05:24:30 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 16450 invoked by uid 500); 27 Nov 2004 05:24:29 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 16423 invoked by uid 99); 27 Nov 2004 05:24:29 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=
X-Spam-Check-By: apache.org
Received-SPF: neutral (hermes.apache.org: local policy)
Received: from ms06.mse1.mailstreet.com (HELO ms06.mse1.mailstreet.com)
 (69.25.50.147)
  by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 26 Nov 2004 21:24:28 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Migrate to SVN?
Date: Sat, 27 Nov 2004 00:24:25 -0500
Message-ID: <8E2D018A78A5A04095667ADF098FF29A035E228A@ms06>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Migrate to SVN?
Thread-Index: AcTUPqpFqQ08FuQwRaK0vmwV7THKFQAAMgVQ
From: "Tim O'Brien" <tobrien@discursive.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

If I might add one more, the process of promoting components from
sandbox to proper will be easier with svn move or copy. =20

One thing I'd like to see going forward is that a component is moved out
of the sandbox upon promotion.  I know it is just an empty directory,
but digester and codec still appear here:
http://cvs.apache.org/viewcvs/jakarta-commons-sandbox/.   =20

Also, I don't want to ever see "waiting for bayard's lock in /blah/blah"
(not singling Henri out) I would like to forget ever knowing about cvs
lock files.
(http://www.network-theory.co.uk/docs/cvsmanual/cvs_88.html)

Tim

> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
> Sent: Friday, November 26, 2004 11:05 PM
> To: Jakarta Commons Developers List
> Subject: RE: Migrate to SVN?
>=20
> > Can you comment on the admin-side advantages of svn ?
>=20
> Elimination of the need for shell accounts, and the ability to shift
load
> from the core infrastructure team to the PMCs.  Trivial project
movement.
> And since we sometimes have to ... <<cough>> ... help recover from
people
> playing around with ",v" files, I would not discount the issue of
> refactoring not creating any issues for infrastructure.
>=20
> Those are a few off-hand.
>=20
> 	--- Noel
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>=20



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org