Sean Schofield wrote:
I think this has dragged on long enough. Apparently there was a bug
introduced in one of the Tomahawk components but I don't think its
worth another prolonged release candidate cycle to address it.
So my proposal is to tag the RC3 release as 1.1.1, rebuild, release.
Then we merge the newest 1.1.1 changes down to the trunk.
There's nothing stopping us from creating a 1.1.2 branch shortly
thereafter and trying to get another stable build working. (This time
the branch should be off of the release point so we don't introduce
new bugs into the release.)
Here's my +1
Well, if you're going to keep the first two digits of the release
version paired up with the JSF standard, then how about going to a
4-digit version number, eg
1.1.0.0
1.1.1.0 (incompatible release)
1.1.1.1 (bugfix release; only last digit changes)
1.1.2.0 (incompatible release)
etc
The last release (1.1.0) is implicitly 1.1.0.0
Calling this release you're currently voting on "1.1.1.0" would at least
give a hint to users that it's a non-backwards-compatible release.
And noting this incompatibility in the release notes document would be
appreciated by users I'm sure.
Regards,
Simon
