X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=bMxkWq7u6KREURKT62p00C8VmqTzrjsoHZ7Ilmw0b8E=; b=dZPCaxyudJvBi4UQm/sG32ToWQ/pRJ/jl3fzb9T6UvfFBcryFIxbHNBF/4UMEuL20F ToYeJHxTZUb6qfnWFVeLGPzdET+3gAM/j24spyRRYs6hRvKV0tL/BgWO0kEFikvvCp30 0P/1s2SGKtkRgbwHrHe+yhsbuM049nlstAERowOvELVfNC1kb4yr78R/rMx/mvWXP4pD BdeyOistDBdmQDhtSPMd4/65eUqq/YKfXBCYnmUtVeRWAvGjC5iFLvyC8mHhBVhf8VbK 4zCyQn9rYekYPRrl6NCzLOeQ6gXHnbSkuZjzqPgmw7rfIsA9Qfl58xBf6MqLtz3YFZnb 0DKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=bMxkWq7u6KREURKT62p00C8VmqTzrjsoHZ7Ilmw0b8E=; b=fYxhNjEsFmvPgkgnCG5afej+0+adqkRw96/zfk+YKHo5WwISqSerwYuRGFreLqX9Rd SuVFOVO/lgbEvUh4s4U/4Y37BkmtOJjlzch1n2mBFLGHEXdivgSIrhn08mklRo+DHOhU jeoaAzFbG6CrYRfuoppcwSLVhtq22QDzmpmSFh+G+M+3IXfDQrG+zCwhMXe4tBSrclNw /9uWr8uOdMS9Zkm0v6K1FQs97+EQ11INDSkqIS/t1uAVVzHQA8ZnWirU/KgTXNCCvc9D meay5d6iup5cwmm3Lj9m6k+vcBBBrY4GkpVTFd/Ip1encrRyWTntTYWbaIp5JHlmixjd p5fA== X-Gm-Message-State: AG10YOTKiDN7cve8CAW7FWmnXo1TBgD1rf301k3wPZbnIgIT9Sv+1Wcb3ne3a58JR0/lGsHoDXG/YJ/3rUEdvA== MIME-Version: 1.0 X-Received: by 10.194.6.165 with SMTP id c5mr28041436wja.88.1453353379501; Wed, 20 Jan 2016 21:16:19 -0800 (PST) In-Reply-To: <201601201958.u0KJwPbo029901@envy.delorie.com> 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> <201601201958 DOT u0KJwPbo029901 AT envy DOT delorie DOT com> Date: Thu, 21 Jan 2016 08:16:19 +0300 Message-ID: Subject: Re: [geda-user] Project leadership From: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 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 On 1/20/16, DJ Delorie wrote: > >> 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. > Main rules I use for myself are: - don't commit code which obviously has serious bugs or crashes; - if I have inadvertently commited something like this, either fix or revert it ASAP; - 'make distcheck' must always work; if it doesn't work, fix it.