We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see ourdocumentation.
There was an error while loading.Please reload this page.
1 parent008fad5 commita16e007Copy full SHA for a16e007
src/tools/RELEASE_CHANGES
@@ -68,15 +68,14 @@ Creating Back-Branch Release Notes
68
69
* Do 'cvs log' on each back-branch and run pgcvslog
70
71
-* Edit and create SGML markup for the most recent branch
+* In CVS HEAD, edit and create SGML markup for the most recent branch
72
+ in that branch's release-N.N.sgml file
73
-* Make copies of the SGML for each branch, then remove items
74
- that do not apply based on cvs logs for that branch
+* Copy this into older branches' release-N.N.sgml files, then remove
75
+ items that do not apply based on cvs logs for that branch (and add
76
+ any that are needed)
77
-* Copy the SGML for each branch into release.sgml in CVS HEAD
-
78
-* Use src/tools/major_release_split to create a release.sgml for
79
- each branch and copy them to the branch's CVS
+* Copy the appropriate release-N.N.sgml files into each back CVS branch
80
81
82
---------------------------------------------------------------------------
src/tools/major_release_split