From: Mark Wielaard <mark@klomp.org>
To: "Karbownik, Anna" <anna.karbownik@intel.com>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Elfutils new release
Date: Wed, 14 Nov 2018 12:24:00 -0000 [thread overview]
Message-ID: <9abefb019b97a1c5e1e4084e4fe243d5d999633b.camel@klomp.org> (raw)
In-Reply-To: <93a4d7c405b39b1c02374dad2d4707f8af58d2ef.camel@klomp.org>
On Wed, 2018-11-07 at 15:33 +0100, Mark Wielaard wrote:
> On Wed, 2018-11-07 at 14:15 +0000, Karbownik, Anna wrote:
> > I'd like to ask you whether you plan to release 0.175 elfutils
> > version?
>
> There are enough (small) new features and bug fixes to do a new
> release. Lets aim for next week.
>
> There are still a couple of patches cooking on the mailinglist and
> there is one outstanding bug related to the new eu-strip --reloc-debug-
> sections-only option with relocations against compressed debug sections
> (but only on armhf and ppc64) which will need to be resolved.
>
> > If so, when are you going to announce it
>
> Once all patches are in and the bug is resolved. Hopefully end of this
> week. I'll announce the intent to do a new 0.175 release on this
> mailinglist. Then after a couple of days, I'll do the release unless
> more issues are found. Hopefully somewhere next week.
Fixing that one bug triggered another bug, updating the buildbot to
Fedora 29 showed a bug and extra testing with gold showed yet another
issue. But everything looks pretty good now. Despite (or maybe thanks
to) the extra fixes going in I feel pretty good about the next release.
I have prepared the source code for the next release and would like to
release it on Friday unless some blocker bug is found before then.
Cheers,
Mark
prev parent reply other threads:[~2018-11-14 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 14:16 Elfutils new reelease Karbownik, Anna
2018-11-07 14:33 ` Elfutils new release Mark Wielaard
2018-11-14 12:24 ` Mark Wielaard [this message]
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=9abefb019b97a1c5e1e4084e4fe243d5d999633b.camel@klomp.org \
--to=mark@klomp.org \
--cc=anna.karbownik@intel.com \
--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).