nhyatt/putty-source
1
0
Fork 0
mirror of https://git.tartarus.org/simon/putty.git synced 2025-02-03 21:52:24 +00:00
Code Issues Projects Releases Wiki Activity

Add bumping version number on trunk to new post-release checklist.

Browse Source 
Also, sometimes `0.XX' is used in the docs as a placeholder for a version
number.

[originally from svn r4700]
This commit is contained in:
Jacob Nevins 2004-10-26 19:32:25 +00:00
parent fd070c31bf
commit a7c8747e0d
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
CHECKLST.txt
View File

@ -72,7 +72,8 @@ It might also be worth going through the documentation looking for
version numbers - we have a couple of transcripts showing the help version numbers - we have a couple of transcripts showing the help
text from the command-line tools, and it would be nice to ensure the text from the command-line tools, and it would be nice to ensure the
whole transcripts (certainly including the version numbers) are up whole transcripts (certainly including the version numbers) are up
to date. to date. Sometimes these are marked in between releases as `0.XX', so
it's worth grepping for that too.
- putty/doc/pscp.but - putty/doc/pscp.but
- putty/doc/plink.but - putty/doc/plink.but
@ -230,4 +231,13 @@ of the tag.
+ Post it to comp.security.ssh. + Post it to comp.security.ssh.
+ Mention it in <TDHTT> on mono. + Mention it in <TDHTT> on mono.
- All done. - Relax (slightly).
After the release
-----------------
The following want doing some time soon after a release has been made:
- If the release was made from a branch, make sure the version number
in _trunk_ CVS is up to date in all the locations listed above, so
that (e.g.) Unix snapshots come out right.