Can revisions also have approximate version # on SF?

>>>>> "KD" == Karl-Dieter Crisman <kcrisman at gmail.com> writes:

    KD> I understand that I can view this if I want to dig far enough
    KD> and understand how revision systems work.  My points are:

    KD> 1) It's a nontrivial amount of work to find this until one has
    KD>    done it
    KD> several times (and even there it's not clear exactly what is
    KD> going on with 5.23 versus 5.23.1 or 5.23.2, one would have to
    KD> know how the Maxima numbering scheme works, which I don't)

The maxima version numbers are fairly easy and typical for open
source.  Major revision 5, minor revision 23.  The final 1 (or 2) are
just updates to the release to fix relatively (?) minor fixes for the
release. 

    KD> 2) For someone unacquainted with the concept of a repository
    KD>    or source
    KD> changes - presumably a nontrivial number of users - there is
    KD> no way they will have a clue when to expect this to show up in
    KD> a binary they can download.

Basically if someone says fixed in rev x.y, it will be in the next
release.  If it says fixed in x.y.z.w, that's a CVS branch and you
won't know if that will make it into the release.  I think branches
have been relatively rare in maxima, so if it says fixed, it will be
in the next release.

    KD> Maybe there is a way to tell SF to automatically create a link
    KD> to the revision log for a given file whenever it sees "Fixed
    KD> in ...  foo.lisp"?

I don't know if that's possible with the current SF setup with CVS.
If maxima should move to git or hg, and also enables Trac, then it's
possible to even update the bug ticket with such information and also
create a link in the ticket to the revision that fixes it.  The link
could even show you a diff of the corresponding changes.  Trac can
also provide a timeline of when things were checked in or the wiki
updated.  

For an example, you can browse through trac.clozure.com/ccl to see
this in action.  See trac.clozuer.com/ccl/ticket/828, for example.

Having said that, I think it takes a fair bit of work to set this all
up and I don't know if sourceforge allows for all of this integration
to happen.  Would be nice, but the old bug reports won't be linked and
I suspect new users won't know to use the trac ticket system.

Ray