From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [DRAFT] doc: 1.6.1 draft release notes
Date: Thu, 31 Dec 2020 20:15:28 +0000 [thread overview]
Message-ID: <20201231201528.3712-1-e@80x24.org> (raw)
Probably going to release before having to run gnulib's
update-copyright again... (And before I crash from this
episode of insomnia :x)
---
Documentation/RelNotes/v1.6.1.wip | 55 +++++++++++++++++++++++++++++++
MANIFEST | 1 +
2 files changed, 56 insertions(+)
create mode 100644 Documentation/RelNotes/v1.6.1.wip
diff --git a/Documentation/RelNotes/v1.6.1.wip b/Documentation/RelNotes/v1.6.1.wip
new file mode 100644
index 00000000..13b41956
--- /dev/null
+++ b/Documentation/RelNotes/v1.6.1.wip
@@ -0,0 +1,55 @@
+From: Eric Wong <e@80x24.org>
+To: meta@public-inbox.org
+Subject: [ANNOUNCE] public-inbox 1.6.1
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Disposition: inline
+
+A small, bugfix release on top of 1.6.0 from September 2020.
+
+Bug fixes:
+
+* MIME header decoding no longer warns on undefined variables,
+ with Perl <5.28. Thanks to a bug report by Ali Alnubani.
+ https://public-inbox.org/meta/DM6PR12MB49106F8E3BD697B63B943A22DADB0@DM6PR12MB4910.namprd12.prod.outlook.com/
+
+* Fixed a message threading bug thanks to a report from Kyle Meyer.
+ "public-inbox-index --rethread --reindex" will be necessary
+ in case of certain messages arrive out-of-order.
+ Link: https://public-inbox.org/meta/87360nlc44.fsf@kyleam.com/
+
+* WWW: per-inbox grokmirror manifests no longer return info
+ for all inboxes, only the root /manifest.js.gz includes all
+ inboxes. This regression appeared in 1.6.
+
+* public-inbox-mda matches List-Id headers insensitively,
+ matching public-inbox-watch behavior. Similarly, List-Id
+ is always indexed lower-cased for boolean matches to avoid
+ matching an incorrect term.
+
+* Newsgroup and Path NNTP headers are now emitted in conformance
+ with RFC 5536 3.1.[45]. Thanks to Andrey Melnikov for the report:
+ https://public-inbox.org/meta/CA+PODjpUN5Q4gBFQhAzUNuMasVEdmp9f=8Uo0Ej0mFumdSwi4w@mail.gmail.com/
+
+* Inotify fixes for public-inbox-imapd users relying on SIGHUP
+ reloads and thousands of watches.
+
+* Read-only daemon fixes around TLS and Linux <4.5 systems
+
+Bugfixes with minor behavior changes:
+
+* The X-Status mbox header is now excluded from imports,
+ just like the Status: header has been for many years.
+ They have no place in public archives and can be privacy
+ concern for people sharing archives.
+
+* WWW prevents deep-linking to attachments to limit abuse
+ vectors. Noticed by Leah Neukirchen:
+ https://public-inbox.org/meta/87imagyap9.fsf@vuxu.org/
+
+There are also several ocumentation fixes from Uwe Kleine-König
+and Kyle Meyer.
+
+Please report bugs via plain-text mail to: meta@public-inbox.org
+
+See archives at https://public-inbox.org/meta/ for all history.
diff --git a/MANIFEST b/MANIFEST
index 6c1cdecc..6a7211b9 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -10,6 +10,7 @@ Documentation/RelNotes/v1.3.0.eml
Documentation/RelNotes/v1.4.0.eml
Documentation/RelNotes/v1.5.0.eml
Documentation/RelNotes/v1.6.0.eml
+Documentation/RelNotes/v1.6.1.wip
Documentation/RelNotes/v1.7.0.wip
Documentation/clients.txt
Documentation/dc-dlvr-spam-flow.txt
reply other threads:[~2020-12-31 20:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201231201528.3712-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.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).