public inbox for
 help / color / mirror / Atom feed
From: Tom de Vries <>
To: Mark Wielaard <>
Subject: Re: dwz 0.14 release?
Date: Mon, 1 Mar 2021 13:40:13 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 3/1/21 12:17 PM, Mark Wielaard wrote:
> Hi Tom,
> On Mon, 2021-03-01 at 11:49 +0100, tdevries wrote:
>> On 2021-02-27 00:37, Mark Wielaard wrote:
>>> 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.
> OK, but could we then pick that as a concrete goal and date for the
> release please?


> There have been requests for a 0.14 release since
> January.

Ahem...  for much longer actually ;)

> I did try to make sure we had up to date lists of pending bugs
> and I believe there are no regressions anymore. That doesn't mean we
> cannot designate some existing bugs as release critical. The temp file
> thingy (PR24275) does indeed seem nasty and it would be great to get it
> fixed.

Yeah, it still gets reported by package maintainers, so I'd really like
to fix this.  I already have a tentative patch (on top of trunk).

> So shall we say that when PR24275 is fixed and no new release critical
> issues (regressions) are found by Monday March 8, then we'll do a 0.14
> release?

Sounds good.

> I am a little afraid we will simply never do a release because there is
> always one more thing to hack on. And the last release was in August
> 2019. There have been lots of bugs fixed since then and some nice new
> features added.

I agree that it's good to do a release now-ish.  I also expect to run
out of dwz-hack-time in a week, so I'm not so afraid of the keep-hacking

> It would be good if we did regular (say every 3 or 6 months) releases.
> Just to make sure people can upgrade and get the new bug fixes and
> features more regularly without having to pick arbitrary git checkouts.

Agreed, regular release are good (though dwz hacking has tended to
happen in rare bursts, so it may not always make sense).  Anyway, I
intended to do a release long ago, but got all tied up in the odr stuff
instead. So thanks for driving this, much appreciated :)

- Tom

  reply	other threads:[~2021-03-01 12:40 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 [this message]
2021-03-05  7:26           ` Tom de Vries
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).