From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] doc: update 1.8 WIP release notes
Date: Fri, 22 Apr 2022 04:31:46 +0000 [thread overview]
Message-ID: <20220422043146.14235-1-e@80x24.org> (raw)
Getting pretty much close to a 1.8 release...
---
Fwiw, I get major anxiety around releases, especially as projects gain
more users... Hell, I'm getting anxiety even proposing patches here :<
Documentation/RelNotes/v1.8.0.wip | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/RelNotes/v1.8.0.wip b/Documentation/RelNotes/v1.8.0.wip
index b662e186..9a9bf9e8 100644
--- a/Documentation/RelNotes/v1.8.0.wip
+++ b/Documentation/RelNotes/v1.8.0.wip
@@ -5,6 +5,8 @@ Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
A minor release focused on bugfixes and minor improvements.
+Upgrades should happen transparently, but downgrading back to
+1.7.0 will likely cause problems for lei users.
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
@@ -20,15 +22,20 @@ Bugfixes:
PublicInbox::WWW: all CR are removed before LF, fixing display of
CR-CR-LF messages.
+ Solver supports SHA-256 code repositories (inbox and lei store support
+ is still pending).
+
Internal updates:
- Reduced dependencies on Inline::C for Linux users.
+ Reduced dependencies on Inline::C for Linux users; Linux users may
+ now use lei with neither Inline::C nor Socket::MsgHdr installed.
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
+ indexes. This may reduce SSD/HDD wear at the expense of disallowing
+ concurrency and data integrity in case of an unexpected shutdown.
Please report bugs via plain-text mail to: meta@public-inbox.org
reply other threads:[~2022-04-22 4:31 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=20220422043146.14235-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).