From: Ricardo Wurmus <rekado@elephly.net>
To: gwl-devel@gnu.org
Subject: Re: bug fix release
Date: Thu, 27 Feb 2020 21:41:33 +0100 [thread overview]
Message-ID: <87eeufiwzm.fsf@elephly.net> (raw)
In-Reply-To: <87d0a9l76x.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> a number of annoying bugs became apparent after the release of 0.2.0.
> They are now fixed. I also refactored the affected code to make it
> easier to understand and test, and added a bunch of tests to be a little
> more confident in the new code.
>
> If you’ve found some other bugs that are not mentioned in NEWS, please
> do report them, so we can squash them before 0.2.1, which I’d like to
> release soon.
I’m planning to release 0.2.1 this Sunday.
--
Ricardo
prev parent reply other threads:[~2020-02-27 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 13:27 bug fix release Ricardo Wurmus
2020-02-27 20:41 ` Ricardo Wurmus [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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eeufiwzm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.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).