Re: cvs: php-src(PHP_5_3) / README.RELEASE_PROCESS

From: Date: Sun, 31 Aug 2008 10:20:53 +0000
Subject: Re: cvs: php-src(PHP_5_3) / README.RELEASE_PROCESS
References: 1 2 3 4  Groups: php.cvs 
Request: Send a blank email to php-cvs+get-52828@lists.php.net to get a copy of this message
On 31.08.2008, at 12:11, Pierre Joye wrote:
Hi Hannes, Lukas. On Sun, Aug 31, 2008 at 12:05 PM, Lukas Kahwe Smith <lsmith@php.net> wrote:
Sounds sensible. Anyways, I would appreciate it if someone who knows would write a howto, so that RMs can verify that things are done properly. I guess in the past Derick took care of a lot of these moves via OS level file system magic. I do not know the details on how this worked. If it was a copy or a move and if there was a cvs rm afterwards or not.
Hannes is right, it can't be a OS Level directory move but at least a copy. Doing a move will change the previous branches and that's not desired. The ideal solution would be: - Filesystem: cp -r php-src/ext/foo pecl/ - cvs rm php-src/ext/foo If the extension is still usable or not dead (unlike sybase but like ming for example), in cooperation with the extension maintainers if any: - create the pecl.php.net/foo package and its content, license, maintainer - create the package.xml, commit - release the package (I can explain the PECL release process if necessary)
sounds good to me. next question .. who can do the FS level cp? i think it would be good to have a list of people RM's can contact for this step. also this way we know the bus-faktor (after all people can disappear temporarily or permanently). regards, Lukas Kahwe Smith smith@pooteeweet.org

« previous php.cvs (#52828) next »