From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by sourceware.org (Postfix) with ESMTPS id A8618389683A for ; Mon, 1 Mar 2021 12:40:14 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A8618389683A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=tdevries@suse.de X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id C8413AFCC; Mon, 1 Mar 2021 12:40:13 +0000 (UTC) Subject: Re: dwz 0.14 release? To: Mark Wielaard Cc: dwz@sourceware.org References: <5b6633862f257bac99fa3fccfde18b931ad10cf2.camel@klomp.org> <59176fae-d720-5a9c-e69c-2553706b7ff1@suse.de> <20210219011612.GK3149@wildebeest.org> <20210226233718.GG3014@wildebeest.org> <8f798710627c532e896bc1c0426310d9d97e1287.camel@klomp.org> From: Tom de Vries Message-ID: <262290e1-2d27-21c3-feee-ec5cee8b851a@suse.de> Date: Mon, 1 Mar 2021 13:40:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <8f798710627c532e896bc1c0426310d9d97e1287.camel@klomp.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, NICE_REPLY_A, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham 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 12:40:16 -0000 On 3/1/21 12:17 PM, Mark Wielaard wrote: > 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. >> >> I'd like to postpone by a week. I've cleaned up odr state, and now I'd >> like to spent some time on other issues. In particular, I'd like to fix >> the temp file thingy. > > OK, but could we then pick that as a concrete goal and date for the > release please? Sure. > There have been requests for a 0.14 release since > January. Ahem... for much longer actually ;) > 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. Yeah, it still gets reported by package maintainers, so I'd really like to fix this. I already have a tentative patch (on top of trunk). > 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? > Sounds good. > 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. > I agree that it's good to do a release now-ish. I also expect to run out of dwz-hack-time in a week, so I'm not so afraid of the keep-hacking scenario. > 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. Agreed, regular release are good (though dwz hacking has tended to happen in rare bursts, so it may not always make sense). Anyway, I intended to do a release long ago, but got all tied up in the odr stuff instead. So thanks for driving this, much appreciated :) Thanks, - Tom