Re: Use "1.7.7" for next release
From: Ashod Nakashian <ashodnakashian_at_yahoo.com>
Date: Sun, 15 Apr 2012 07:05:02 -0700 (PDT)
----- Original Message -----
I meant the two project versions won't diverge indefinitely. Sure each patch can result in a mismatch (assuming TSVN continues to use the 3rd number for patches) but as long as both projects use the same major.minor numbers, they realign again at every significant release. Which is my point; patch numbers aren't all that relevant. What a user typically cares about are the major.minor version of SVN (which dictates features and compatibility etc.) and that they have the latest patch for *that* major.minor.
In other words, if I'm using TSVN and I care to use version 1.7 of SVN features, I'll make sure I have the latest patch for 1.7 of TSVN. If that's 1.7.9, then that's the best that TSVN provides, regardless what the patch number of SVN stands at. If I care to know the exact SVN patch TSVN is linked against, I have ample places to look for this information. (and if I know of an SVN patch that TSVN doesn't yet provide, then I'll either wait or switch to a different 3rd party SVN product.)
If a different versioning scheme should prove less confusing to TSVN users (I was never confused by this issue and I'm a rather old user of both projects), then that can be adopted, but it's very reasonable that TSVN has its own patches (whether to fix their bugs or even SVN bugs/workarounds) and that can't match the patch number of SVN.
So if 100% alignment isn't possible, making SVN realign with TSVN more often won't help much. It's best to keep SVN independent of downstream projects (as many voiced) and that TSVN clearly advertises the patch number as their own without implied matching with SVN patches. That way the user's won't have an expectation that is wrong half the time (as is the case now).
This is an archived mail posted to the Subversion Dev mailing list.