Re: Updating release version to 22.1

[Lennart Borgman]

Maybe the effort of changing the version number should be saved to the CVS
as some kind of script?

----- Original Message ----- 
From: "Miles Bader" <address@hidden>

The problems caused by the current "mess" (21.4 released to mean
something else, 22.1 chosen for next release) would have happened
regardless of what scheme was chosen (including all of your wacky
ones), because what occured is that an extra real release was added in
between the last real release and the designated next real release.
No amount of futzing around with pre-release names would have changed
that.