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=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=mfhoGWxe+VOUEiI0TdTX3+PBsr0Ee9q9dvhMyOHBk2I=; b=MvK5R3Z6VeQWEZv+PwI/wSFJcSIRHmHlJ2FYY7Y6ZKRksytxY4B93q4T3JqDJaSiEn Y2YMGGuAXuCKxnqb6meGOy4xJHTgzlG1yb05frQqsPJL7/oY2t2ZKOKGYi5bH4wr7T89 UF7KRh/9KY+3QFBj1NyCTTtODG4TBgxS3aNuBuhM6gD8iZb8lV1z8WEe7qQL8vI6jx4g vQ6A2ckppwaT4FW0epbB9zmXBlZGrC1Ryz4Kp33o120MusOGBA37yjOWo0eg0AdNRZmn jJIapncejdzTghPGy6kBHS+ZUH2BQvAEZJWifOu1h3DXXnQV03ZprqDPkOit+KUAGDiI WgIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=mfhoGWxe+VOUEiI0TdTX3+PBsr0Ee9q9dvhMyOHBk2I=; b=Qng1shX1eil1idDEsThBxsjhj3iWylgrOYG21yz9Irxdfpo8JzRKPGnPlCuy5KsaXX MtiMgKjNHRIEFFqngWOrrG0cqtltX2dFKgmeZXfEnkyI5RRuJxM5BUMWFsq4jsBbdcUT SLWYUvFJJt/rqBRt71I+YqNLQQ8temze1DgqxOrjbz2+sxCfWKjpkycy9IZGzPV9G7hM LSeXHjDFmUX9k43KFYQWbq8zwuWerc4eMi7akSkpE66vjTqCdkKDi0QZtgzRBFI9YMX8 yDl8FJ6OtKD3cnBQTcKhQnJFstheaLHSqJyQXqm7XMxPC8eX8T1DdRe2hCwIJ3R7yCGj alXg== X-Gm-Message-State: ALoCoQlwt87M2NBPiQQs83MbtD5RSCPJg8A0BQFt7jNjjP4f5lLcf13oVzPVZhpGYadbjAfh0XTMPRM3QOk8XyRMLuu/xJI3Hg== X-Received: by 10.25.148.142 with SMTP id w136mr11486685lfd.31.1453311027537; Wed, 20 Jan 2016 09:30:27 -0800 (PST) Date: Wed, 20 Jan 2016 20:30:24 +0300 From: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Project leadership Message-ID: <20160120173024.GB16858@localhost.localdomain> Mail-Followup-To: geda-user AT delorie DOT 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> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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 Thu, Dec 31, 2015 at 08:57:53PM +0100, Roland Lutz wrote: ... > So the options to handle this are: > (a) Don't merge the code until the defect is fixed. > (b) Have "make distcheck" fail as a reminder that the code doesn't work right. > (c) Hack the test driver so a failed test doesn't cause "make distcheck" to abort. > (d) Add the defect to the documentation as a known bug and set the corresponding tests to XFAIL. (e) File a bug report for the defect and don't switch on testing for it until it will be fixed. Ideally 'make distcheck' should never fail. This is a requirement for new releases by convention and we should allow a new release at any time. Imagine a developer has made some changes and left the project, died, married at last... and nobody understands how to fix her Scheme/Python/Haskell code ;) Cheers, Vladimir