Write release notes for 4.2.2
I’ve updated the changelog on the stable branch already. On top of the 4.2.1 ones, here are the new changes:
* Bugfixes - Avoid the Upgrader proposing to upgrade to the version that's already running (Closes: <del><a class='issue tracker-1 status-3 priority-7 priority-default closed child' href='/code/issues/17425' title='“double-upgrades” after 4.1.1 → 4.2 (IUKv1) → 4.2.1 (IUKv2)'>Bug #17425</a></del>) - Avoid 2 minutes delay while rebooting after applying an automatic upgrade (Closes: <del><a class='issue tracker-1 status-3 priority-4 priority-default closed child' href='/code/issues/17026' title='Long delay while rebooting after applying an automatic upgrade'>Bug #17026</a></del>) * Build system - IUK generation: don't make all files in the SquashFS diff owned by root, otherwise an upgraded system cannot start (Closes: <del><a class='issue tracker-1 status-3 priority-7 priority-default closed child' href='/code/issues/17422' title='Broken upgrade path from 4.2 to 4.2.1: GDM doesn't start'>Bug #17422</a></del>)
I assume the build system changes are irrelevant.
|Blocks Tails - Feature #17247: Core work 2020Q1 → 2020Q2: Technical writing||Confirmed|
#2 Updated by intrigeri 2020-01-13 10:13:33
Another difference that impacts the release notes: direct upgrades will only be provided from 4.2. Users of Tails << 4.2 will be proposed to upgrade to 4.2 (just like it is right now), and once they’ve restarted on 4.2, they’ll be proposed to upgrade to 4.2.2.
wiki/src/news/version_4.2.1.mdwn, to ensure it does not end up being published by mistake, but I know you’ll be able to salvage + rename it yourself :)
#3 Updated by sajolida 2020-01-14 09:54:24
- Status changed from Confirmed to Needs Validation
- Assignee changed from sajolida to intrigeri
I’m glad you deleted version_4.2.1.mdwn. It’s typically something I could have forgotten :)
Release notes are ready in 16b8b5f258.