[Development] Branching 5.0

BRM bm_witness at yahoo.com
Sat Dec 1 06:02:34 CET 2012

> From: d3fault <d3faultdotxbe at gmail.com>

> Sent: Friday, November 30, 2012 11:25 PM
> Subject: Re: [Development] Branching 5.0
> On 11/30/12, Thiago Macieira <thiago.macieira at intel.com> wrote:
>>  He says that the converse usually holds true. First of all, converses
>>  usually
>>  do not hold true. Conditions that are both necessary and sufficient are the
>>  exception, not the rule. Second, it does not hold in this case either.
> I never said most/all converses hold true, just that that particular
> one usually does.
> 99.99997% of "programming projects" (@Lars saying Qt is not a Linux
> distribution) use "stable" and "release" interchangeably.

I would be to differ there.

As Thiago pointed out, release implies stable but stable does not imply release,
and that holds true for the vast majority of software.

To draw from Version Control systems such as Subversion, one very common
practice is for trunk to be "prestine" - stable, compilable, and ready for release at any time -
and all work to be done in branches. It is not released, but it is at all times stable.

Now if you only talk to the user-lists of many open source projects, then you will probably get
that view that they are interchangeable. Talk to the developer lists, and you'll see the difference.


More information about the Development mailing list