I know this isn't the place for this question, but I figured that here'd be as good a place to as as anywhere else as it's been mentioned.
Should we avoid releasing a set version number, (eg 0.3, 0.4) and release a compiled svn revision? That way we wouldn't have the panic over sorting out a new release, and people could keep more upto date?
In that case they can subscribe to the svn?
Software numbering is fairly well defined logic behind it and folks will know that 0.4 is newer than 0.3 etc... whereas they may not know what the heck the svn revision number means.
("They're up to version 499?!")
How about releasing r500 a 0.4 (or is that 0.5 now?
) and then a weekly or monthly compile as Rnnn? We could keep a history then and it'd make checking back through the code easier to see when it last worked? LoL
Well, for what purpose? There was a genuine singularity between 0.3 and 0.4. and
there have been truly major changes since 04... but we're talking years and months elapsed time respectively.
While I setup up the binary release package to be easily updated I don't expect version level changes very often... unless we're going for a v.0.4.0012 level of granularity?
I think that a "Current SVN" text box with a link to lmop's site is the way to handle that.