X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <20160120210035.3859.qmail@stuge.se> Date: Wed, 20 Jan 2016 22:00:35 +0100 From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Releaseability of gEDA code Mail-Followup-To: geda-user AT delorie DOT com References: <20151223195846 DOT 8392 DOT qmail AT stuge DOT se> <20151229155647 DOT GA3752 AT localhost DOT localdomain> <20151229175222 DOT GD3752 AT localhost DOT localdomain> <96A12FC1-E09C-4D63-8346-5A62FDAB4228 AT sbcglobal DOT net> <20160120173024 DOT GB16858 AT localhost DOT localdomain> <201601201903 DOT u0KJ3Lx4026878 AT envy DOT delorie DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201601201903.u0KJ3Lx4026878@envy.delorie.com> 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 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