Why don't we tag those revisions now in SVN? (I can't as I don't have commit rights.) The tags are useful when you need to debug issues in released versions. You can easily switch to a particular tag to repro an issue and then switch to a later version to verify that the issue has been fixed. I have the NH SVN repo mirrored in Git so that switching between tagged NH versions takes literally seconds.
https://github.com/JamesKovacs/nhibernate James On Apr 20, 9:47 am, Fabio Maulo <[email protected]> wrote: > Missed > btw if you need the rev-number you can see the releasenotes.txt > Build 3.2.0.Aplha2 (rev5715) > Build 3.2.0.Aplha1 (rev5664) > Build 3.1.0.GA (rev5425) > Build 3.0.0.GA (rev5290) > > and/or the > JIRAhttp://216.121.112.228/browse/NH#selectedTab=com.atlassian.jira.plugi... > > <http://216.121.112.228/browse/NH#selectedTab=com.atlassian.jira.plugi...>For > the next final release (GA) I'll try to remember the generation of the tag, > promise!! > > On Wed, Apr 20, 2011 at 12:41 PM, Oskar Berggren > <[email protected]>wrote: > > > Hmmm, shouldn't there be a tag for 3.1.0 in > >https://nhibernate.svn.sourceforge.net/svnroot/nhibernate/tags?And > > possibly for the 3.2 alphas also? Or what is the policy? > > > /Oskar > > -- > Fabio Maulo
