On Wed, Mar 26, 2008 at 06:09:50PM -0700, Will Coleda wrote: > Basically, user problems are reported against a *release*. Anyone > reporting a problem against something more fine grained than a release > is a developer, and we should expect them to be able to use their own > version control tools, or re-rsync, or somehow coordinate with us. > > Please comment if you think we missed a critical use case on the > revision number. > > So, given consensus on not needing the revision number... we can > remove all the code for calculating, testing and displaying it: > [...] > We do wish to keep PARROT_VERSION (generated for > include/parrot/config.h), but any references to PARROT_REVISION must > go. > > Since this isn't a feature, we can avoid the normal deprecation cycle > and rip this out before the next release; Let's hold off a few days to > give time for responses other than "+1", however. (but +1s are most > welcome to avoid Warnocking).
+1 Outstanding analysis and reporting. Great work! Pm
