[PATCH] doc: update 1.8 WIP release notes

[PATCH] doc: update 1.8 WIP release notes

[Eric Wong]

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