public inbox for dwz@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>
Cc: dwz@sourceware.org
Subject: Re: dwz 0.14 release?
Date: Fri, 5 Mar 2021 08:26:32 +0100	[thread overview]
Message-ID: <df2f99fb-7fb5-e8f5-3b3e-8f93518ceb65@suse.de> (raw)
In-Reply-To: <c017f2292e1d46e8318744e42f149920@suse.de>

On 3/1/21 11:49 AM, tdevries wrote:
> On 2021-02-27 00:37, Mark Wielaard wrote:
>> Hi,
>>
>> I propose we do a release on Monday March 1. Unless people think there
>> are still some release critical issues that need to be resolved first.
>>
> 
> I'd like to postpone by a week.  I've cleaned up odr state, and now I'd
> like to spent some time on other issues.  In particular, I'd like to fix
> the temp file thingy.
> 

That's fixed now.

I've done some more bugzilla enhancement marking, now the only
non-enhancement open PRs are:
- PR24441 - Some crashes found by fuzzing
- PR25459 - Forward pseudo-reference triggers error

AFAIC, from the open PR perspective, we're good for the release.

I'll do one more round of gdb testing against dwz, and then hopefully we
can release on Monday.

Thanks,
- Tom

  parent reply	other threads:[~2021-03-05  7:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 12:06 Mark Wielaard
2021-02-11  9:15 ` Tom de Vries
2021-02-12 10:08   ` Mark Wielaard
2021-02-19  1:16     ` Mark Wielaard
2021-02-26 23:37       ` Mark Wielaard
2021-03-01 10:49         ` tdevries
2021-03-01 11:17           ` Mark Wielaard
2021-03-01 12:40             ` Tom de Vries
2021-03-05  7:26           ` Tom de Vries [this message]
2021-03-05 16:24             ` Tom de Vries
2021-03-08  7:14               ` Tom de Vries
2021-03-08  7:22                 ` 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=df2f99fb-7fb5-e8f5-3b3e-8f93518ceb65@suse.de \
    --to=tdevries@suse.de \
    --cc=dwz@sourceware.org \
    --cc=mark@klomp.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).