From: Mark Wielaard <mark@klomp.org>
To: elfutils-devel@sourceware.org
Subject: Preparing for elfutils 0.169
Date: Tue, 02 May 2017 11:17:00 -0000 [thread overview]
Message-ID: <1493648561.31726.145.camel@klomp.org> (raw)
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
reply other threads:[~2017-05-01 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1493648561.31726.145.camel@klomp.org \
--to=mark@klomp.org \
--cc=elfutils-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).