[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "What To Release" vs "How To Release"

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Thu, 22 May 2008 18:59:13 -0400

Karl Fogel <kfogel_at_red-bean.com> writes:
> The point is that these two topics are entirely independent: anything
> we decide for "What To Release" is achievable; in fact, most outcomes
> are achievable in more than one way -- which is why we muddied our
> "What To Release" discussions with "How To Release" issues.
> Let's please stop mixing these topics. The important topic here is
> "What To Release". Once we decide that, we can have a much quicker
> discussion about "How To Release".

I forgot to mention this important corollary:

The fact that any particular change has/hasn't been merged to the 1.5.x
branch has *no bearing* on whether it is included in 1.5.0. There have
been some statements implying that once something is merged in, that
means we're going to release it in 1.5.0. I wrote the above mail to
dispel this myth once and for all.

Having a version control system means we get to *choose*. Yes, changes
that have been merged into the 1.5.x branch, or even just changes listed
in STATUS, are destined to come out in some 1.5.x release someday. But
for any given change, the question of which specific release it is first
published in is entirely under our control. Nothing about merging a
change to a branch, or proposing it in a STATUS file, or anything else,
forces us to include it in 1.5.0. We have a tool sophisticated enough
to give us all the choices we could want, as long as we're willing to
exercise those choices.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-23 00:59:28 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.