Topic: Automating application version numbering...
So I finally got my first app deployed, though I've discovered a few critical bugs that slipped through unit testing.
I'm looking around for solutions surrounding automating version/revision numbering. I've seen one mini tutorial that create a Version model and uses the after_deploy task to stick the SVN revision number into the version. I assume I could extend that to also handle rollback. However that's just a revision number. I'd rather a more complete solution that allows for some sense of version.major.minor.patch. Ideally I think it should be hooked into cap or svn hooks rather than requiring manually tagging in SVN before every deploy.
Has anyone seen anything along these lines or rolled their own solution they'd be willing to share?