Re: Importing packages into CVS

From: Date: Wed, 28 Mar 2007 00:23:16 +0000
Subject: Re: Importing packages into CVS
References: 1 2 3 4 5 6 7  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-46073@lists.php.net to get a copy of this message
Jon Parise wrote:
On Tue, Mar 27, 2007 at 05:12:02PM -0700, Joshua Eichorn wrote:
What is the point of hosting a _copy_ of the source code on cvs.php.net? PEAR currently permits active development to occur in an external source control repository so the cvs.php.net would always be out-of-date. Do you want it to be hosted on cvs.php.net as a reference resource? The code will never be current, and the active external repository can already be used as a reference. 
      My point is that this is solvable.
Do yo want to allow PEAR QA folks to commit changes to a package's code? The code will become forked from the active development line. 
      Commiting to a fork could be a reasonable short term solution if the maintainer wasn't available for whatever reason, and an emergency bug fix was needed.
Do you want to archive a historic copy of the code, perhaps on a per-release basis? pear.php.net already has a copy of the source code on a per-release basis. 
      This code is available in the tarballs but not easily accessible since its all compressed, and has no tools associated with it.
I think the biggest benefit is allowing for easy access to all the code by QA scripts. I'm running my own source repo for HTML_AJAX so i too have worries but I do want to help QA out, seems to be that with commit time mirroring this could be useful. One time mirroring just seems worthless. -josh

« previous php.pear.dev (#46073) next »