X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Wed, 20 Jan 2016 14:58:25 -0500 Message-Id: <201601201958.u0KJwPbo029901@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (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> <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> Reply-To: geda-user AT delorie DOT com > Clearly, master is always more likely to have bugs, as a result of > integration of new features (patch commit or merge - whatever), but I think > it is always best to TRY and keep master in a state where we expect it > works, and expect we COULD branch a release from it. True, but there's a wide range of options (and paranoia levels) between "good enough to play with" and "good enough to release". What I don't want is to make it so difficult and/or expensive to get work into master, that work never gets into master. We need to be willing to accept *some* risk in order to promote progress.