From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: add WIP release notes for 1.8
Date: Fri, 11 Mar 2022 05:21:43 +0000 [thread overview]
Message-ID: <20220311052143.33857-1-e@80x24.org> (raw)
1.8 will be a minor release, soon (I initially expected to
release it in December, but was side-tracked). Major features
will be for 1.9.
---
Documentation/RelNotes/v1.8.0.wip | 36 +++++++++++++++++++++++++++++++
MANIFEST | 1 +
2 files changed, 37 insertions(+)
create mode 100644 Documentation/RelNotes/v1.8.0.wip
diff --git a/Documentation/RelNotes/v1.8.0.wip b/Documentation/RelNotes/v1.8.0.wip
new file mode 100644
index 00000000..b662e186
--- /dev/null
+++ b/Documentation/RelNotes/v1.8.0.wip
@@ -0,0 +1,36 @@
+To: meta@public-inbox.org
+Subject: [WIP] public-inbox 1.8.0
+MIME-Version: 1.0
+Content-Type: text/plain; charset=utf-8
+Content-Disposition: inline
+
+A minor release focused on bugfixes and minor improvements.
+
+lei users may experience duplicate messages in Maildirs if attempting to
+downgrade from 1.8.0 to 1.7.x. public-inbox-* tools are unaffected and
+may downgrade freely.
+
+Bugfixes:
+
+ Numerous test fixes thanks to NixOS developers.
+
+ Long-running daemons are more robust in case of corrupt blobs
+ or crashes of git-cat-file processes
+
+ PublicInbox::WWW: all CR are removed before LF, fixing display of
+ CR-CR-LF messages.
+
+Internal updates:
+
+ Reduced dependencies on Inline::C for Linux users.
+
+New features:
+
+ The --dangerous flag is now supported in public-inbox-index and
+ public-inbox-extindex to use the Xapian::DB_DANGEROUS flag for initial
+ indexes. This may reduce SSD/HDD wear at the expense of
+
+Please report bugs via plain-text mail to: meta@public-inbox.org
+
+See archives at https://public-inbox.org/meta/ for all history.
+See https://public-inbox.org/TODO for what the future holds.
diff --git a/MANIFEST b/MANIFEST
index ca840210..92c9f891 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -12,6 +12,7 @@ Documentation/RelNotes/v1.5.0.eml
Documentation/RelNotes/v1.6.0.eml
Documentation/RelNotes/v1.6.1.eml
Documentation/RelNotes/v1.7.0.eml
+Documentation/RelNotes/v1.8.0.wip
Documentation/clients.txt
Documentation/common.perl
Documentation/dc-dlvr-spam-flow.txt
reply other threads:[~2022-03-11 5:21 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=20220311052143.33857-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).