X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <569FF8A0.70400@iee.org>
Date: Wed, 20 Jan 2016 21:14:08 +0000
From: "M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Releaseability of gEDA code
References: <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> <201601201903 DOT u0KJ3Lx4026878 AT envy DOT delorie DOT com> <20160120210035 DOT 3859 DOT qmail AT stuge DOT se>
In-Reply-To: <20160120210035.3859.qmail@stuge.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:Cr6aew7Rl214hUdTU9FSzuKnaol9TZA/k/uUG82vNcXDavITZck
 3T4KlIaaEtREpB3S+L08yD+IrfXbl1gJmlbbrVkUeccaYeAH4oqUgHA9Htqrh0ngwu5lzUz
 Ubcaj8jFfLA4y7Ytop3kVNNFIMKWPjhm/LcoaFCdvRuAni3tvQWRTH0RahCqEy8kkgAVm/J
 2RSjocQbuoT+HWmCaq2UA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:+sXS68meJIw=:z3uoiryRJM1CQ6Y/BL3gQm
 WWvoxUa+FJp4D1wPbib3E/cYu+wdMOc9L7qNIpnTh+NwgGA6XWpYWhPJU8nHGQJhxOZaVn8Vf
 rjzvMKe+zRRifGsERQVJ+DVXzq+1SqNoPm1ksK84S0JG4sthjCE4Nf+vwTNkXRZPJYxniLRSD
 BBWPXLG9AzRX/rkyN1iqT9czn0HB15uT//UWkJvAoPKYujYZ6wWjGOZ6UGSq8po13UVUr486f
 iYUsxSvcqlnlLzYm4X1pXVf5/VlJwsFOLcxk7CSKD6Lt6dAYlBbgUFW3HVQTzCzBhLbxXeLtg
 9uW9O4JQUgds9cuKLDAYer6OzVbtbpdmcCq/kC/cfifE0Q2RL6x2qc7eEmSe7tlac07HBZK85
 joIQwAquaVrF24EzpiRL95bsRr9c0LFqxACF9L/XO6Hk/20m3NnucQCxeP7zBYK6Q5/EgbnDd
 9O734jqtR8Sr7xf8idMxS+DhiivNBPt2VFy3x/WA5BvlQkh9flSvpWAMJsWS9p5LSEAyMOlQ/
 0GYAgmJsZjSU/q2lpAgdJqjjZFLXmaoQRYY+4BczHZt9m2JmHVkg1KD7YZ6z/snk7/783x3bO
 sgo5YVYeHlIfLOpyRrThIWxSLzw8kBg5MTX150FSe1RnwO6t9HwacUiYw+WlsN7bdIQmL1qFA
 pBKPiGFYfG7p7XB3vxicWJgEZ4KkAE5duhqKpxty/kUYBeNqyGBpMRuZz5CctxhQ4uzLD9EjS
 NB6YhaURvTxerjkb7rXKRpPKmxeVdpxaHoWe365UyVIbk/JOW3AgOhvTj8sYwwrCPfClqLXqZ
 Z0VqalcYTbHDA+anFxIRPePqmfdJA==
Reply-To: geda-user AT delorie DOT com

On 20/01/16 21:00, Peter Stuge (peter AT stuge DOT se) [via
geda-user AT delorie DOT com] wrote:
> DJ Delorie wrote:
>> Do we want to change how we do development?
> For the sake of simplicity I am a strong proponent of having master
> be releaseable at all times.
>
> This requires more careful development, I think that's a good thing.
>
> I find it acceptable to introduce some breakage in a random release,
> as long as it also gets fixed quickly, and if master is always
> releaseable then it's trivial to make a bugfix release.
>
>
> //Peter
I think you can run two 'tiers' of release successfully, or even three
if you want to follow the debian naming strategy ..
- "stable" is tested, bug fixed, no known issues (and is maintained as
such with minor revisions)
- "beta" - new features, no major crashes .. but odd bugs may prevail
- "unstable" (which is usually where the VCS lives) - may or may not
build (but normally does), crashes minimised, bugs likely

If you maintain a consistent set of branches/tags for these purposes
(trunk/master remains typically 'unstable') then it should be possible
to develop/merge and fix bugs all in parallel without too much issue.

MJE