Or we could have other proposals: anyone cares to propose them?
I would love to see some way to tag new versions of contrib modules. A large percentage of time-consuming (arguably time-wasting) support requests I get is because people are using an old 4.5 version of a given module. But how should they know that I merged in a whole string of fixes in the past week? Unless they know how to review CVS, there is no way for them to know. (Currently I have to get them to open the module file in a text editor and to look at the Id tag at the top of the file)
What about using letters for modules? 4.5a, 4.5b, 4.5c.
It has the potential of getting out of control, after reaching 4.5z (and given the long release cycle of Drupal itself, it could easily happen with an actively developed module). I suggested 4.5.x.20050213, because if contrib packages are made daily, this is clear, it can be automatically detected, if a new version should be shipped or not (whether there was CVS activity on the module or not on that day, or better worded: before the last release), and it has no way to run out of possibilities. If releases can only be made daily. IMHO it should help a lot, if these versions would be done automatically when needed, without human intervention. It also increases the possibility of shipping something broken though... Goba