Naming the Windows installer

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So we've had some discussions in the bug tracker about whether the
current names for the windows installers are understandable.

By default, the python installers use distutils to name themselves, and
it names them as:
  bzr-$VERSION.win32-py$PYVERSION.exe
or
  bzr-1.18rc1.win32-py2.5.exe

And then we manually created the 'setup.exe' name as:
  bzr-setup-1.18rc1.exe

I want to add the 'build version' to this naming scheme, and to date,
I've been putting it as part of the bzr version number, such as:
 bzr-1.18rc1-1.win32-py2.5.exe
and
 bzr-setup-1.18rc1-1.exe

On IRC and elsewhere, Robert has mentioned that his favorite is:
 bzr-1.18rc1-setup-1.exe

Which is generally pretty nice. It is fairly clear that 1.18rc1 is the
version of bzr, and -1 is the version of the installer.

However, that doesn't seem to translate into anything nice for the
python installers:
 bzr-1.18rc1.win32-py2.5-1.exe
looks a lot more like it is a version of python (2.5-1)
 bzr-1.18rc1.win32-1-py2.5.exe
 bzr-1.18rc1.win32-py2.5-setup-1.exe
...
?

I noticed in Martin's last update to the "six-month stable release"
document he said:

> +Binary installers should use a version number like '2.0-1' or '2.0beta1-1'
> +so that the last component just reflects the packaging version, and can be
> +incremented if a new installer is made with no upstream source changes.


Which would hint and using:
 bzr-1.18rc1-1.setup.exe
and
 bzr-1.18rc1-1.win32-py2.5.exe

That would honestly be the easiest for me to get automated, as I would
probably just add a variable in "setup.py" (probably an ENV var, etc)
that would get passed into the 'version=' information.

I'm interested in feedback, though. Certainly the complaint still holds
that "1.18rc1-1" looks like '-1' is a version of bzr and not a version
of the installer. (And Martin's comment could just have been codifying
my current practice, and not really thinking a lot about it independently.)

For now, I'm just going to stick with the last form, because it is
consistent with what I've been doing.

And on the plus side, installers for 1.18rc1 have finally been built.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqDO/UACgkQJdeBCYSNAANEZgCfWNtddbBbr0BREe93Y/7on+sN
X4wAn3YcykqhdMWMP2ZWSxaDXm6P9lT5
=+TcI
-----END PGP SIGNATURE-----