Version number and other tweakings prior to the 0.58 release.

[originally from svn r5598]

CHECKLST.txt

@@ -65,7 +65,8 @@ orders them correctly with respect to releases):
 
  - putty/LATEST.VER
 
-The Windows installer script (_three_ times, on consecutive lines):
+The Windows installer script (_three_ times, on consecutive lines,
+and again in a subsequent comment):
 
  - putty/windows/putty.iss
 

LATEST.VER

@@ -1 +1 @@
-0.57
+0.58

doc/faq.but

@@ -1013,10 +1013,8 @@ leave. You can do that automatically, by running the command
 the currently logged-in user on \i{multi-user systems}.)
 
 If PuTTY was installed from the installer package, it will also
-appear in \q{Add/Remove Programs}.
+appear in \q{Add/Remove Programs}. Older versions of the uninstaller
-\#{XXX-REMOVE-BEFORE-RELEASE - replace with: Older versions of the uninstaller do not}
+do not remove the above-mentioned registry entries and file.
-Uninstallation does not currently
-remove the above-mentioned registry entries and file.
 
 \S{faq-dsa}{Question} How come PuTTY now supports \i{DSA}, when the
 website used to say how insecure it was?

doc/pgpkeys.but

@@ -12,13 +12,11 @@ accurate idea of what each signature guarantees.
 This description is provided as both a web page on the PuTTY site, and
 an appendix in the PuTTY manual.
 
-As of the next release, all of the PuTTY executables will contain
+As of release 0.58, all of the PuTTY executables contain fingerprint
-\#{XXX-REMOVE-BEFORE-RELEASE: fix this up for forthcoming release
+material (usually accessed via the \i\c{-pgpfp} command-line
-As of release 0.58, all of the PuTTY executables contain}
+option), such that if you have an executable you trust, you can use
-fingerprint material (usually accessed via the \i\c{-pgpfp}
+it to establish a trust path, for instance to a newer version
-command-line option), such that if you have an executable you trust,
+downloaded from the Internet.
-you can use it to establish a trust path, for instance to a newer
-version downloaded from the Internet.
 
 (Note that none of the keys, signatures, etc mentioned here have
 anything to do with keys used with SSH - they are purely for verifying

doc/plink.but

@@ -43,7 +43,7 @@ use Plink:
 
 \c Z:\sysosd>plink
 \c PuTTY Link: command-line connection utility
-\c Release 0.XX
+\c Release 0.58
 \c Usage: plink [options] [user@]host [command]
 \c        ("host" can also be a PuTTY saved session name)
 \c Options:

doc/pscp.but

@@ -41,7 +41,7 @@ use PSCP:
 
 \c Z:\owendadmin>pscp
 \c PuTTY Secure Copy client
-\c Release 0.XX
+\c Release 0.58
 \c Usage: pscp [options] [user@]host:source target
 \c        pscp [options] source [source...] [user@]host:target
 \c        pscp [options] -ls [user@]host:filespec

mac/version.r

@@ -2,7 +2,7 @@
  * Current PuTTY version number.  Minor is in BCD
  */
 #define VERSION_MAJOR 0x00
-#define VERSION_MINOR 0x57
+#define VERSION_MINOR 0x58
 
 resource 'vers' (1, purgeable) {
 #ifdef RELEASE

windows/putty.iss

@@ -15,12 +15,12 @@
 
 [Setup]
 AppName=PuTTY
-AppVerName=PuTTY version 0.57
+AppVerName=PuTTY version 0.58
-VersionInfoTextVersion=Release 0.57
+VersionInfoTextVersion=Release 0.58
-AppVersion=0.57
+AppVersion=0.58
 ;FIXME -- enable this when we've got it going for individual EXEs too
 ;         and are committed to the version numbering scheme.
-;VersionInfoVersion=0.57.0.0
+;VersionInfoVersion=0.58.0.0
 AppPublisher=Simon Tatham
 AppPublisherURL=http://www.chiark.greenend.org.uk/~sgtatham/putty/
 AppReadmeFile={app}\README.txt