From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id EF79E3857C4E for ; Fri, 15 Apr 2022 10:40:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org EF79E3857C4E Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from tarox.wildebeest.org (83-87-18-245.cable.dynamic.v4.ziggo.nl [83.87.18.245]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id BCBD23000429 for ; Fri, 15 Apr 2022 12:40:55 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id D2792413CD15; Fri, 15 Apr 2022 12:40:54 +0200 (CEST) Message-ID: <95e2503a1cc016eb340020e3f73a825a25f05b41.camel@klomp.org> Subject: Proposing elfutils-0.187 for Monday 25 April From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Fri, 15 Apr 2022 12:40:54 +0200 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=-3.7 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: elfutils-devel@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Elfutils-devel mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2022 10:40:59 -0000 Hi, It has been 5 months since elfutils 0.186 was released. There have been more than 70 commits since then. And 20 bugs closed. I propose we do an elfutils 0.187 release Monday 25 April. There are still a couple of unreviewed patches: https://patchwork.sourceware.org/project/elfutils/list/ I'll try to go over them all before the release. If there are any other issues left, please let me know. Lets try to do the next release in 3 months, so there isn't such a big gap between releases. Cheers, Mark