From: Eric Wong <e@yhbt.net>
To: meta@public-inbox.org
Subject: [PATCH] doc: some 1.3.0 release notes updates
Date: Tue, 14 Jan 2020 07:56:26 +0000 [thread overview]
Message-ID: <20200114075626.18955-1-e@yhbt.net> (raw)
---
Documentation/RelNotes/v1.3.0.eml | 32 ++++++++++++++++++++++++-------
1 file changed, 25 insertions(+), 7 deletions(-)
diff --git a/Documentation/RelNotes/v1.3.0.eml b/Documentation/RelNotes/v1.3.0.eml
index 11806ccd..9000ccaf 100644
--- a/Documentation/RelNotes/v1.3.0.eml
+++ b/Documentation/RelNotes/v1.3.0.eml
@@ -6,10 +6,10 @@ Content-Type: text/plain; charset=utf-8
Many internal improvements to improve the developer experience
and long-term maintainability.
-Many of the internal improvements focused on being able to avoid
-Perl startup time in tests. "make check" now runs about 50%
-faster than before, and the new "make check-run" can be around
-30% faster after being primed by "make check".
+Some of the internal improvements involve avoiding Perl startup
+time in tests. "make check" now runs about 50% faster than
+before, and the new "make check-run" can be around 30% faster
+than "make check" after being primed by "make check".
Most closures (anonymous subroutines) are purged from the
-nntpd, -httpd and WWW code paths to make checking for memory
@@ -22,21 +22,39 @@ leaks easier.
* the work-in-progress Xapian.pm SWIG bindings are now supported
in addition to the traditional Search::Xapian XS bindings.
- Only SWIG bindings are packaged for OpenBSD.
+ Only the SWIG bindings are packaged for OpenBSD.
-* IPC::Run is no longer used in tests
+* Plack is optional for users who wish to avoid web-related components
+
+* Filesys::Notify::Simple is optional for non-watch users
+ (but Plack will pull it in)
* improved internal error checking and reporting in numerous places
-
+
+* IPC::Run is no longer used in tests
+
+* Email::Address::XS used if available (newer Email::MIME
+ requires it), it should handle more corner cases.
+
* PublicInbox::WWW
- "nested" search results page now shows relevancy percentages
+ - many solver bugs fixed
- solver works on "-U0" patches using "git apply --unidiff-zero"
+ - solver now compatible with git < v1.8.5 (but >= v1.8.0)
- raw HTML no longer shown inline in multipart/alternative messages
(v1.2.0 regression)
+ - reduced memory usage for displaying multipart messages
+ - static file responses support Last-Modified/If-Modified-Since
+ - avoid trailing underlines in diffstat linkification
* public-inbox-httpd / public-inbox-nntpd:
- MSG_MORE used consistently in long responses
- fixed IO::KQueue usage on *BSDs
+ - listen sockets are closed immediately on graceful shutdown
+ - missed signals avoided with signalfd or EVFILT_SIGNAL
+
+* public-inbox-nntpd:
+ Y2020 workaround for Time::Local
* public-inbox-watch
- avoid memory leak from cyclic reference on SIGHUP
reply other threads:[~2020-01-14 7:56 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=20200114075626.18955-1-e@yhbt.net \
--to=e@yhbt.net \
--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).