Re: [PHP-PEAR] Re: [PHP-CVS] cvs: php4 /pear/Experimental README/pear/Experimental/HTML Menu.php

[email protected] ((Stig Sæther Bakken)) 10 Mar 2001 01:23:22 +0100
Newsgroups php.pear,php.pear.dev
Message-ID <[email protected]>
[Jon Parise <[email protected]>]
> On Fri, Mar 09, 2001 at 11:33:54PM +0100, Stig Sther Bakken wrote:
> 
> > 4. Code staging (dealing with experimental code etc.)
> > 
> > We need to be able to register some additional information about each
> > package.  We could use the website/database for this.  One of the
> > attributes we can register is how mature the code (or a given release)
> > is, and I think that could replace today's "Experimental".
> 
> Perhaps a simple file (XML?) in the top of each package directory
> could contain the infortmation for that package.  It would be trivial
> to periodically import the data contained therein into a database or
> web page.

Yes, it's either one way or the other.  The advantage of having the
database as the source is that it works just as well for packages that
do not originate from the php.net CVS repository, and it's generally
easier to extract than update XML data from a database. :-)

> > If a package needs to fork off an experimental development cycle, I
> > think CVS branches are the best thing to use, with sufficient user
> > education. :-)
> 
> Branches are an excellent approach when used properly.  The
> post-experimenal-cycle merges might be difficult for those who aren't
> already experienced with cvs, however.

Yes, that's my main problem with it, too.  But you don't really avoid
this kind of problem (fixing conflicts during a merge) with other
solutions either?

> > If we decide that CVS branches are too difficult, awkward or whatever,
> > it could perhaps be done on the filesystem level instead, using a
> > subdirectory instead of a branch.
> 
> I prefer the branching approach over the file system approach.
> 
> As a side note, maybe Perforce would be a better choice than cvs for
> this sort of repository?  Just a suggestion.  I like them both. =)

What is Perforce?  (IMHO, any CVS replacement has to offer
_significant_ benefits if I am ever to consider a move of anything.
CVS is just too well-integrated with people's software and minds. :-)

 - Stig

-- 
  Stig Sæther Bakken <[email protected]>
  Fast Search & Transfer ASA, Trondheim, Norway