From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Preparing for elfutils 0.160
Date: Wed, 20 Aug 2014 12:28:30 +0200 [thread overview]
Message-ID: <1408530510.3610.7.camel@bordewijk.wildebeest.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
Hi,
It has been 3 months since elfutils 0.159, since then we have seen more
than 20 commits, fixing several bugs and adding some new features
(ppc64le ELFv2 abi, arm thumb support, unstrip -F, dwarf_cu_getdwarf,
dwarf_cu_die). There are some bugs in the bugtracker, that I want to go
over, but none of them look like regressions:
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&component=elfutils
It would be nice to get some more fixes in, but I don't believe any of
them are block a new release. Is there something someone thinks should
go in before we do a release?
I would like to push for a 0.160 release in a week, around Wednesday 27
August. And then aim for the next release in ~3 months again, before the
end of the year, to keep things moving forward.
Cheers,
Mark
next reply other threads:[~2014-08-20 10:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 10:28 Mark Wielaard [this message]
2014-08-25 20:36 Mark Wielaard
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=1408530510.3610.7.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).