diff options
| author | Robert Haas <rhaas@postgresql.org> | 2010-09-21 00:25:07 -0400 |
|---|---|---|
| committer | Robert Haas <rhaas@postgresql.org> | 2010-09-21 06:59:30 -0400 |
| commit | 8f00f73dc240a034668023f6d1ab18695bb1be32 (patch) | |
| tree | 0cd8f1f7d2c41ae7ea6f170ae5a01aa56c3ae1b9 | |
| parent | 1b984d43e54a969da26277d913a41ffd5ccfc1e8 (diff) | |
| download | postgresql-8f00f73dc240a034668023f6d1ab18695bb1be32.tar.gz postgresql-8f00f73dc240a034668023f6d1ab18695bb1be32.zip | |
Remove various mentions of CVS from src/tools/RELEASE_CHANGES.
| -rw-r--r-- | src/tools/RELEASE_CHANGES | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/src/tools/RELEASE_CHANGES b/src/tools/RELEASE_CHANGES index 76379975c82..91f8742f701 100644 --- a/src/tools/RELEASE_CHANGES +++ b/src/tools/RELEASE_CHANGES @@ -6,7 +6,7 @@ For All Releases (major, minor, beta, RC) (by packager) (beta) * Release notes - o scan cvs logs, use pgcvslog and flags in comments + o run git log and, if useful, src/tools/git_topo_order o update doc/src/sgml/release.sgml o run spellchecker on result o add SGML markup @@ -31,7 +31,7 @@ For Major Releases (in addition to the above) * Release notes - o search with commit message text to find CVS commit file changes + o use git log or src/tools/git_topo_order to find the relevant commits o check completion of items that have been marked as completed at http://wiki.postgresql.org/wiki/Todo o remove completed TODO items @@ -62,7 +62,7 @@ For Major Releases Starting a New Development Cycle ================================ -* Create a branch in CVS for maintenance of the previous release +* Create a branch in git for maintenance of the previous release * Increment the major version number in src/tools/version_stamp.pl @@ -76,16 +76,16 @@ Starting a New Development Cycle Creating Back-Branch Release Notes ================================== -* Do 'cvs log' on each back-branch and run pgcvslog +* Run src/tools/git_topo_order to generate a list of relevant commits -* In CVS HEAD, edit and create SGML markup for the most recent branch - in that branch's release-N.N.sgml file +* On the git master branch, edit and create SGML markup for the most recent + branch in that branch's release-N.N.sgml file * Copy this into older branches' release-N.N.sgml files, then remove - items that do not apply based on cvs logs for that branch (and add + items that do not apply based on commit logs for that branch (and add any that are needed) -* Copy the appropriate release-N.N.sgml files into each back CVS branch +* Copy the appropriate release-N.N.sgml files into each back branch --------------------------------------------------------------------------- |