docs: add release announcement for the 4.6.0 suite to NEWS - #3288
docs: add release announcement for the 4.6.0 suite to NEWS#3288andylemin wants to merge 4 commits into
Conversation
|
@rdmark Ready for your editing pass.. a bunch of stuff that should probably be trimmed, and I suspect missing some things? |
Introduce the public announcement for the coordinated release of Netatalk 4.6.0, Netatalk Client 1.0, and the new netatalk.io website, ahead of the itemized 4.6.0 changelog section. The narrative groups the release cycle's changes into themes for a general audience: server performance, strict cache coherency and the locking overhaul, multi-protocol coexistence with Samba, feature complete Spotlight search, the move to SQL CNID backends, security hardening, the client's graduation to production status, and the new website.
2c611b1 to
517eaa9
Compare
Remove the suite-overview section that duplicated the opening paragraph, drop filler openers, and lead each section with its facts. All figures and claims are unchanged.
1be7f9f to
627e56d
Compare
|
@andylemin this is a nice write-up, I think most items are covered, but I'll go through the commit log is your idea to have a write-up like this in NEWS.md for every release, or is this a special one-off? up until now I've been writing release notes like this in the body of the GitHub releases, but I see a value in keeping a copy of our release notes under revision control as well. the NEWS.md file is already massively large, accumulated contents since 1992 ;) |
| with server signature verification and authenticated session binding. | ||
| * **Compatibility across the whole AFP timeline**: AFP 2.x servers, Mac | ||
| OS X file sharing, Time Capsules, Netatalk 4, AFP 3.4 — with Zeroconf | ||
| discovery, full UTF-8, and classic Mac code pages. |
There was a problem hiding this comment.
the only classic codepage supported right now is MacRoman, but porting over the others that Netatalk already supports will be trivial :)
There was a problem hiding this comment.
This will actually be very important.. For AFP3 clients Netatalk supports setting today;
mac charset = UTF8-MAC # NFD (Normalization Form Canonical Decomposition - decomposed)
unix charset = UTF8 # NFC (Normalization Form Canonical Composition - composed)
vol charset = UTF8 # NFC (Normalization Form Canonical Composition - composed)
https://netatalk.io/manual/en/afp.conf.5#charset-options
This is better than the default (MAC_ROMAN) as conversion of UTF8 to/from UTF8-MAC is faster than the conversion to/from MAC_ROMAN (Ie, it only requires composition conversion rather than a full charset table conversion).
And UTF-8 supports modern language characters. So we definitely want Netatalk-client to speak UTF8-MAC.
Going forward; in the AFP4 / AFP-POSIX draft spec I have added native client support for UTF-8 to align with AFPS etc which allows for charset to be "passthrough" end to end (disk-to-wire-to-disk).
There was a problem hiding this comment.
I was thinking of the other regional language charsets primarily -- MacGreek, MacHebrew, MacCyrillic and so on
what you point out is arguably even more important
Mention NAS devices, correct the client project's age to two years, name Zeroconf service discovery, add legacy Classic Mac OS authentication, scope code page support to MacRoman, cite kio-afp as a libafpsl consumer, and extend the multi-protocol section to NFS and local accessors.
c3ae610 to
43acc8b
Compare
|
@rdmark All changes done. Let me know if there is anything else? Feel free to pull this PR and edit as you see fit.
My thinking was just that NEWS.md is on the home page of the website. We should add the same text to the Release notes on github as well so its shown there too?
I don't see an issue with the length, it's the provenance trail.. |
rdmark
left a comment
rdmark
left a comment
There was a problem hiding this comment.
I think this is great!
one fast follow (mostly note to self) is that we need to "port" the v4.5.1, v4.5.2 changelogs over to main
https://github.com/Netatalk/netatalk/blob/branch-netatalk-4-5/NEWS.md
Serving AFP was already possible almost anywhere; mounting it was effectively Apple-only. Lead with that constraint being removed rather than mere continuity.
|
📊 Performance DashboardCommit: 🔥 Spectest (AFP 3.4) - FlameGraphNetatalk Code-time: 2.3% · Runtime: 62s · Stacks: 1052 🔥 Click the preview to open the interactive flamegraph (zoom + search). 🔝 Top 10 leaf functions
📈 Speedtest (AFP 3.4) - PerfGraphPeak Read: 8350 MB/s (+12.0% vs hist avg 7454.5 MB/s; min 6219 / max 9526 over 30 PRs) 🔝 Throughputs per operation (vs. historical average)
⏱️ Lantest (AFP 3.4) - LatencyGraphAvg total runtime: 4507 ms (+23.9% vs hist avg 3638.9 ms; min 2122 / max 4529 over 30 PRs) 🐢 All operations (avg runtime, in test order, vs. historical average)
Run baseline: median op-test delta +25.1%, MAD 1.7%. Adj Δ% shifts each delta by the median; standouts ≥5% in bold. A large MAD means the run did not move uniformly — read the adjusted column with caution. |
|
|
||
| This cycle closed more than twenty CVEs, hardened every authentication | ||
| method (DHX, DHX2, SRP), tightened wire-format parsing throughout, and | ||
| added an unprivileged single-user mode. Even the classic AppleTalk |
There was a problem hiding this comment.
it's looking more and more like we won't do the single-user mode in this release, so let's remove this phrase
2 participants
What this adds
A public release announcement at the top of
NEWS.md, ahead of the itemized 4.6.0 changelog, covering the coordinated release of Netatalk 4.6.0, Netatalk Client 1.0, and the new netatalk.io website.The announcement is written for a general audience and groups work into themes:
Coordination
Review points