From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112]) by sourceware.org (Postfix) with ESMTPS id D5D3D3896837 for ; Mon, 1 Mar 2021 11:17:13 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org D5D3D3896837 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id DB51F301BC15; Mon, 1 Mar 2021 12:17:10 +0100 (CET) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id 9342A41A0387; Mon, 1 Mar 2021 12:17:10 +0100 (CET) Message-ID: <8f798710627c532e896bc1c0426310d9d97e1287.camel@klomp.org> Subject: Re: dwz 0.14 release? From: Mark Wielaard To: tdevries Cc: dwz@sourceware.org Date: Mon, 01 Mar 2021 12:17:10 +0100 In-Reply-To: References: <5b6633862f257bac99fa3fccfde18b931ad10cf2.camel@klomp.org> <59176fae-d720-5a9c-e69c-2553706b7ff1@suse.de> <20210219011612.GK3149@wildebeest.org> <20210226233718.GG3014@wildebeest.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) Mime-Version: 1.0 X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: dwz@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Dwz mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Mar 2021 11:17:15 -0000 Hi Tom, On Mon, 2021-03-01 at 11:49 +0100, tdevries wrote: > On 2021-02-27 00:37, Mark Wielaard wrote: > > I propose we do a release on Monday March 1. Unless people think > > there > > are still some release critical issues that need to be resolved first. >=20 > I'd like to postpone by a week. I've cleaned up odr state, and now I'd= =20 > like to spent some time on other issues. In particular, I'd like to fix= =20 > the temp file thingy. OK, but could we then pick that as a concrete goal and date for the release please? There have been requests for a 0.14 release since January. I did try to make sure we had up to date lists of pending bugs and I believe there are no regressions anymore. That doesn't mean we cannot designate some existing bugs as release critical. The temp file thingy (PR24275) does indeed seem nasty and it would be great to get it fixed. So shall we say that when PR24275 is fixed and no new release critical issues (regressions) are found by Monday March 8, then we'll do a 0.14 release? I am a little afraid we will simply never do a release because there is always one more thing to hack on. And the last release was in August 2019. There have been lots of bugs fixed since then and some nice new features added. It would be good if we did regular (say every 3 or 6 months) releases. Just to make sure people can upgrade and get the new bug fixes and features more regularly without having to pick arbitrary git checkouts. Thanks, Mark