Re: Version numbers vs SVN

[Chris Travers <..hidden..>]

Perhaps we should have the following policy:

The specific release should be mentioned in the commit log unless it
is the current svn revision that's being copied over?  That's what I
have been trying to do.  Checking the commit history to see what it
says....

Revision 4317 - Directory Listing
Modified Wed Feb 15 09:01:21 2012 UTC (5 days ago) by einhverfr
tagging 1.3.11, svn 4316

Revision 4315 - Directory Listing
Modified Wed Feb 15 00:04:16 2012 UTC (5 days, 9 hours ago) by einhverfr
Belatedly tagging 1.3.10, as svn 4263

Best Wishes,
Chris Travers
On Sun, Feb 19, 2012 at 8:02 PM, Michael Richardson <..hidden..> wrote:
>
> I'm finding it difficult to determine exactly which commit 1.3.10 and
> 1.3.11 releases were made from.  I can guess that 1.3.11 is somewhere
> after commit:
>
>  r4306 | einhverfr | 2012-02-13 08:14:33 -0500 (Mon, 13 Feb 2012) | 1 line
>  Version number updates
>
> but it's not clear to me how many after this might also be included.
> Of course, SVN stucks about putting tags into this... could I request a
> clear release comment?
>
> --
> ]       He who is tired of Weird Al is tired of life!           |  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
> ] ..hidden.. http://www.sandelman.ottawa.on.ca/ |device driver[
>   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
>                       then sign the petition.
>
> ------------------------------------------------------------------------------
> Try before you buy = See our experts in action!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-dev2
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel