From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [ANNOUNCE] public-inbox 1.9.0
Date: Sun, 21 Aug 2022 02:36:59 +0000 [thread overview]
Message-ID: <2022-08-21T023659Z-public-inbox-1.9.0-rele@sed> (raw)
Upgrading:
lei users need to "lei daemon-kill" after installation to load
new code. Normal daemons (read-only, and public-inbox-watch)
will also need restarts, of course, but there's no
backwards-incompatible data format changes so rolling back to
older versions is harmless.
Major bugfixes:
* lei no longer freezes from inotify/EVFILT_VNODE handling,
user interrupts (Ctrl-C), nor excessive errors/warnings
* IMAP server fairness improved to avoid excessive blob prefetch
New features:
* POP3 server support added, use either public-inbox-pop3d or
the new public-inbox-netd superserver
* public-inbox-netd superserver supporting any combination of HTTP,
IMAP, POP3, and NNTP services; simplifying management and allowing
more sharing of memory used for various data structures.
* public-inbox-httpd and -netd support per-listener .psgi files
* SIGHUP reloads TLS certs and keys in addition to config and .psgi files
* "lei reindex" command for lei users to update personal index
in ~/.local/share/lei/store for search improvements below:
Search improvements:
These will require --reindex with public-inbox-index and/or
public-inbox-extindex for public inboxes.
* patchid: prefix search support added to WWW and lei for
"git patch-id --stable" support
* text inside base-85 binary patches are no longer indexed
to avoid false positives
* for lei users, "lei reindex" now exists and is required
to take advantage of aforementioned indexing changes
Performance improvements:
* IMAP server startup is faster with many mailboxes when using
"public-inbox-extindex --all"
* NNTP group listings are also faster with many inboxes when
using "public-inbox-extindex --all"
* various small opcode and memory usage reductions
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.
reply other threads:[~2022-08-21 2:37 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=2022-08-21T023659Z-public-inbox-1.9.0-rele@sed \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).