[phc-internals] [phc] r3395 committed - Flesh out RELEASE.HOWTO where I had been unclear.
phc at googlecode.com
phc at googlecode.com
Tue Oct 26 14:22:09 IST 2010
Revision: 3395
Author: paul.biggar
Date: Tue Oct 26 06:21:18 2010
Log: Flesh out RELEASE.HOWTO where I had been unclear.
http://code.google.com/p/phc/source/detail?r=3395
Modified:
/trunk/doc/RELEASE.HOWTO
=======================================
--- /trunk/doc/RELEASE.HOWTO Fri Sep 10 01:13:36 2010
+++ /trunk/doc/RELEASE.HOWTO Tue Oct 26 06:21:18 2010
@@ -1,31 +1,38 @@
-0. svn update
- - do not omit this step.
-
-1. Update the Changelog
-
-2. Run misc/makerelease.sh
- - check the test results are correct
-
-3. Upload the release to phpcompiler.org
- - unzip the docs into doc/
- - put all files in src/archive
-
-4. Update phpcompiler.org
- - news
- - downloads
- - documentation
- - .htaccess - doc links
- - contribute - Have you thanked the contributors?
- - ChangeLog goes in the repository
-
-5. Update code.google.com
- - upload the files
-
-6. Tag the release
-
-7. Announce on phc-general
- - major releases on comp.compilers and php.general
-
-8. Update freshmeat
-
-9. Does anything need to be merged back to trunk?
+How to do a release of phc.
+
+ 0. svn update
+ - do not omit this step.
+
+ 1. Update the Changelog
+ - In theory, this should be every change made in this release. However,
+ this is very expensive in time, for very little gain, so high-level
+ fixes are probably better.
+
+ 2. Run misc/makerelease.sh
+ - check the test results are correct
+
+ 3. Upload the release to phpcompiler.org
+ - unzip the docs into doc/
+ - put all files in src/archive
+
+ 4. Update phpcompiler.org
+ - news
+ - downloads
+ - documentation
+ - .htaccess - doc links
+ - contribute - Have you thanked the contributors?
+ - ChangeLog goes in the repository
+
+ 5. Update code.google.com
+ - upload the files
+
+ 6. Tag the release using svn
+
+ 7. Announce on phc-general
+ - major releases on comp.compilers and php.general
+
+ 8. Update freshmeat
+
+Minor releases only:
+
+ 9. Does anything need to be merged back to trunk?
More information about the phc-internals
mailing list