Can revisions also have approximate version # on SF?

>
> 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.

Okay, I thought perhaps, but since the log only had the major and
minor I didn't know what the .z part would stand for - in particular,
whether release x.y.z would have any bugfixes made up to then, or only
the most pressing ones, with other left for x.(y+1). Thanks for that
clarification.

> 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

> 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
>
> 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

Yup - we use Trac with Sage.   It's not perfect, but I do like some of
those sorts of options.  However, I am a mathematician, not a
professional programmer, so I'm not interested in telling anyone to
switch revision systems or anything - that leads to flamewars :)  I
just wondered whether SF made it easy to do this.

Thanks much.