From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110830 invoked by alias); 1 May 2017 14:22:45 -0000 Mailing-List: contact elfutils-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: elfutils-devel-owner@sourceware.org Received: (qmail 110752 invoked by uid 89); 1 May 2017 14:22:43 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=BAYES_05,KAM_LAZY_DOMAIN_SECURITY,T_COMPENSATION autolearn=no version=3.3.2 spammy=compensate, integration, H*M:145, H*MI:145 X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_05,KAM_LAZY_DOMAIN_SECURITY,T_COMPENSATION autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 01 May 2017 14:22:42 +0000 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 043C130010E1 for ; Mon, 1 May 2017 16:22:42 +0200 (CEST) Received: by tarox.wildebeest.org (Postfix, from userid 1000) id E2AA84003067; Mon, 1 May 2017 16:22:41 +0200 (CEST) Message-ID: <1493648561.31726.145.camel@klomp.org> Subject: Preparing for elfutils 0.169 From: Mark Wielaard To: elfutils-devel@sourceware.org Date: Tue, 02 May 2017 11:17:00 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) Mime-Version: 1.0 X-IsSubscribed: yes X-SW-Source: 2017-q2/txt/msg00128.txt.bz2 Hi hackers, It is May already and 0.168 was released 4 months ago. So it is really time to get a new release out (we normally do one every 3 months). There have been a couple of crasher fixes that would be good to make sure are in a stable (distro) release. So I would like to do a 0.169 release this week. The frame pointer unwinder patches for x86_64, i686 and aarch64 seem good to go in before release. And I'll do another scan over the submitted patches on the mailinglist from the last 2 weeks. I most likely won't apply the big gnulib modules integration patch before the release. I am afraid that will be a little too disruptive right for a release. But I do think that is a good thing to integrate. So if we integrate that soon after the release then we can test it a little better for 0.170. I also didn't have time to finish my DWARF5 work. So that too would also go into the next release. We could do the next release a bit quicker to compensate for 0.169 being a month late and do 0.170 after 2 months (end of June/start of July). Cheers, Mark