Greg Stein <gstein@lyra.org> writes:
> No... it needs to be called 0.14.5.
>
> It is quite possible that people grabbed the 0.14.4 tarball. We want to
> ensure that when problems are reported, that we know which tarball they
> grabbed.
>
> And yes, this also means that some of the changes since 0.14.4 will be
> incorporated into the new 0.14.5 (e.g. xml logging and Karl's prop work).
>
> Release numbers are cheap. Use them. :-)
<displeasure level="very mild">
Next time, let's please call it "0.14.4b" or "0.14.4.2" (just by
tweaking the minor number in svn_version.h appropriately).
Release numbers are only cheap when used like rational numbers :-).
Because we called it 0.14.5, a bunch of target milestones in the issue
tracker had to get shifted, and the change to the status page gets
bigger. Also, it's a little misleading to increment the first minor
number for such a small change -- that is, for a tiny bugfix to an
interim release, rather than a full interim release. 0.14.5 had a
definition before now, and we just released something that didn't meet
that definition. Not a huge deal, just makes it a little harder for
someone following the project to figure out what's going on.
Version number aside, I purposely waited until after the release to
commit that prop work. Although it's probably fine this time, in
general, we should look at the trunk commits between the inital
release and the bugfix release, determine whether they are really 100%
innocuous, and not hesitate to make a temporary branch for the bugfix
release(s).
"Branches and tags are cheap. Use them. :-)"
-Karl
P.S. I've shifted the milestones and will take care of
project_status.html later.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 30 21:38:25 2002