question re --version flag

Let be begin by congratulating the xmonad developers on the release of version 0.6. I have been a delighted user since 0.4. Thank you for a fantastic product. I saw on the announcement of the 0.6 release that a new flag had been introduced: " --version: print *xmonad*'s version " Naturally, I tried it first thing after installing v 0.6, and was surprised to get the result "xmonad 0.5". I am left wondering what's up. I deleted the v 0.5 binary and seemingly installed v .6. If the flag is indeed new, then I must have v 0.6, and am seeing an oversight in a version number. Is that what I am seeing, or did v 0.5 also have a --version flag? David Cabana

drcabana:
Let be begin by congratulating the xmonad developers on the release of version 0.6. I have been a delighted user since 0.4. Thank you for a fantastic product.
Yay :)
I saw on the announcement of the 0.6 release that a new flag had been introduced: " --version: print xmonad's version " Naturally, I tried it first thing after installing v 0.6, and was surprised to get the result "xmonad 0.5". I am left wondering what's up. I deleted the v 0.5 binary and seemingly installed v .6. If the flag is indeed new, then I must have v 0.6, and am seeing an oversight in a version number. Is that what I am seeing, or did v 0.5 also have a --version flag? David Cabana
It was in fact an oversight :) I've patched it, and the darcs version has the correct flag. THe release process has changed to ensure this doesn't happen next time. Thanks for the report! -- Don

* Don Stewart
I've patched it, and the darcs version has the correct flag.
Aren't you going to patch released tarballs? It'll be a shame for us. Like that with version mismatch in haddock (0.4 instead of 0.5), but more noticeable. After all, what's the point of releasing 0.6 if users don't notice it? *jokingly* -- Roman I. Cheplyaka (aka Feuerbach @ IRC)

roma:
* Don Stewart
[2008-01-28 17:21:58-0800] I've patched it, and the darcs version has the correct flag.
Aren't you going to patch released tarballs? It'll be a shame for us. Like that with version mismatch in haddock (0.4 instead of 0.5), but more noticeable.
After all, what's the point of releasing 0.6 if users don't notice it? *jokingly*
We certainly won't mutate the released tarballs (packagers don't like doing that) -- and impurity is bad anyway ;) -- Don
participants (3)
-
David Cabana
-
Don Stewart
-
Roman Cheplyaka