X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Wed, 20 Jan 2016 14:03:21 -0500
Message-Id: <201601201903.u0KJ3Lx4026878@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20160120173024.GB16858@localhost.localdomain>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] Project leadership
References: <20151222193859 DOT 26898 DOT qmail AT stuge DOT se>
 <20151223202851 DOT 637d5b1f AT jive DOT levalinux DOT org>
 <20151223195846 DOT 8392 DOT qmail AT stuge DOT se>
 <CAM2RGhS2bg=Rjuq6oEeOacV7PfUENy_jq7dxag=vWsUbdH6pAQ AT mail DOT gmail DOT com>
 <20151229155647 DOT GA3752 AT localhost DOT localdomain>
 <CAM2RGhSLND5+JSSj=1cUPUhzkTCK6d7NZ61QL-eViZRccY5LqA AT mail DOT gmail DOT com>
 <20151229175222 DOT GD3752 AT localhost DOT localdomain>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1512311656190 DOT 1475 AT newt>
 <96A12FC1-E09C-4D63-8346-5A62FDAB4228 AT sbcglobal DOT net>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1512311916190 DOT 12724 AT newt> <20160120173024 DOT GB16858 AT localhost DOT localdomain>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> and we should allow a new release at any time.

We usually run in phases - during development we're not "release
ready" but then we switch to release mode to stabilize and clean up
master.  Many project run in cycles like this.  Do we want to change
how we do development?  IMHO wherever the most development is
happening, is both going to be a bit unstable and going to be where
all the stuff you want to release is.

On the PCB side we create a branch for each release, and those
branches must always be "release ready" just in case, but not master.
Master is where things come together, so we have to allow for some
chaos.