Re: svn: /web/php/trunk/include/ version.inc

On Tue, Jun 28, 2011 at 19:04, Stas Malyshev <smalyshev@gmail.com> wrote: > Hi! > > So this was what README.RELEASE_PROCESS said: > 2. Update `web/php/trunk/include/version.inc` (x=major version > number) >  a. `$PHP_x_RC` = "5.3.0RC1" >  b. `$PHP_x_RC_DATE` = "06 September 2007" > 3. Commit those changes: >  a. `svn commit web/qa/trunk web/php-bugs/trunk web/php/trunk` > I guess it is out of date - so what should be done now? Should it just be > removed and only QA and bugs part left? I don't understand whats wrong with those instructions? You added 2c) "update $RELEASES" which is wrong, and you missed editing php-bugs before attempting to commit. I do however notice that bunch of stuff in phpweb believes 5.2 and 5.3 and current versions, so even if you added 5_4 variable it wouldn't do anything - but thats trivial fix. A quick list of things I remember that needs to be done; For QA releases you need to modify 4 sites - phpweb - modify version.inc Set $PHP_5_4_RC = "whatever the release is"; Set $PHP_5_4_RC_DATE = "whatever the current date is"; - qaweb - Do whatever you did (this changed recently but your changes look ok) - bugsweb Add the RC to the list of versions somewhere - peclweb Add the RC to the list of versions somewhere For the next RC of the same series: - Update the $...._DATE variable with the current date - Replace the previous entry in qaweb - Replace the previous version entry in peclweb and bugsweb For a new stable after RC you need to cleanup the rc stuff - phpweb - Set the $..._RC variable to = false - qaweb remove the entry - replace the rc entry with a proper entry bugsweb and peclweb - follow whatever the release instructions say As for pearweb, I think they already use our release feed to populate their version information, bugsweb and peclweb do not iirc. -Hannes