Re: Releasing 1.6

Martin Furter wrote:
> And STATUS already contains a few things for the next micro release.
> Who cares if it's called 1.5.2 or 1.6.0?

We should *all* care about such things. A new minor version may mean new
APIs we live with for the foreseeable future. It may mean working copy
format bumps. It may mean new repository formats. These aren't the kinds
of things you just push onto the user base every 3 months because you're in
some kind of unnatural hurry to whip out releases. Each minor release comes
with promises; every promise paid for with maintenance effort. Please don't
be so flippant about such matters.

Now, it might be true that right now, we've none of these "promise problem
points" queued in the trunk since 1.5.0 was branched. If that's the case,
we aren't paying that particular maintenance cost right now, so that doesn't
count against doing 1.6.0 over 1.5.2. But as a general statement ... well,
see my first paragraph.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand