Skip to content

Commit

Permalink
Flesh out RELEASE.HOWTO where I had been unclear.
Browse files Browse the repository at this point in the history
  • Loading branch information
pbiggar committed Oct 26, 2010
1 parent f86d4fd commit d2152ef
Showing 1 changed file with 29 additions and 22 deletions.
51 changes: 29 additions & 22 deletions doc/RELEASE.HOWTO
Original file line number Diff line number Diff line change
@@ -1,31 +1,38 @@
0. svn update
- do not omit this step.
How to do a release of phc.

1. Update the Changelog
0. svn update
- do not omit this step.

2. Run misc/makerelease.sh
- check the test results are correct
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.

3. Upload the release to phpcompiler.org
- unzip the docs into doc/
- put all files in src/archive
2. Run misc/makerelease.sh
- check the test results are correct

4. Update phpcompiler.org
- news
- downloads
- documentation
- .htaccess - doc links
- contribute - Have you thanked the contributors?
- ChangeLog goes in the repository
3. Upload the release to phpcompiler.org
- unzip the docs into doc/
- put all files in src/archive

5. Update code.google.com
- upload the files
4. Update phpcompiler.org
- news
- downloads
- documentation
- .htaccess - doc links
- contribute - Have you thanked the contributors?
- ChangeLog goes in the repository

6. Tag the release
5. Update code.google.com
- upload the files

7. Announce on phc-general
- major releases on comp.compilers and php.general
6. Tag the release using svn

8. Update freshmeat
7. Announce on phc-general
- major releases on comp.compilers and php.general

9. Does anything need to be merged back to trunk?
8. Update freshmeat

Minor releases only:

9. Does anything need to be merged back to trunk?

0 comments on commit d2152ef

Please sign in to comment.