Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45434
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 83.243.58.134 as permitted sender)
To: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 29 Aug 2009 16:33:48 +0200
Message-ID: <1251556428.22693.20.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Really going to 5.3.1RC1
From: johannes@php.net (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

I thought I sent the warning out on thursday but can't find it in my
internals folder therefore the notice:

  We certainly should get 5.3.1 rolling and therefore I'm planning RC1
  on Tuesday evening European time


I'm not toooo used to subversion therefore I'd like some comments about
this procedure:

1) Monday evening branch of a release branch owned by me
   $ svn cp branches/PHP_5_3 branches/php_5_3_1
   Question A: using php as in our tags or PHP as in our branches?
   Question B: can svn merge be used to get changes from PHP_5_3 or is a
               manual merge better?
2) Tuesday: Change the version
   $ vi branches/php_5_3_1/main/php_version.h etc.
3) making the branch a tag
   $ svn mv branches/php_5_3_1 tags/php_5_3_1
4) merge the tag into the PHP_5_3 branch
   $ cd branches/PHP_5_3 && svn merge ../tags/php_5_3_1
   The idea would be that the release appears in the
   branch's history and nothing is being lost
   Question: Does that make any sense?
5) Change the version to RC2-dev
   $ vi branches/PHP_5_3/main/php_version.h etc.


Feedback on this procedure and svn usage welcome. If this doesn't work
out the procedure can be changed for the next release and I guess a RC
is a better test than a "proper" release.

johannes