Feature #17558
Write release notes for 4.5~rc1
0%
Description
Hi,
I’m not sure this ticket is really a duplicate of Feature #17303, but as far as I understood what we wanted to do, it shouldn’t be…
It was pointed out by my fellow RMs that we would need some help from technical writers for the 4.5~rc1 announcement (that we would usually just quickly copy/sed from the previous one, without involving you), as this release candidate contains a lot of important changes.
I’ve just pushed a doc/changelog-4.5-rc1 branch with a draft changelog entry (that I must confess I haven’t entirely proofread yet), so that you can benefit from a head start on the release announcement writing front. Feel free to let me know if you edit the changelog in that branch, so that I can merge improvements/fixes back into the proper branch(es) when I’m reaching the relevant point of the release process.
(Full disclosure: I wasn’t convinced what I had been doing with the devel/@testing@ branches was right, so I need to do some more homework before resuming the release process; hopefully having the changelog around means you can start without me.)
Also, @anonym wanted to help you, and this draft was started → https://pad.riseup.net/p/kYQ9G0VIFniAsfK5ADnW
Given the current status, I’m assuming images might be available during the European evening, so we might be looking at a publication somewhen Friday afternoon.
Subtasks
History
#1 Updated by CyrilBrulebois 2020-03-26 19:58:33
Most up-to-date changelog now lives in the testing branch. :)
#2 Updated by sajolida 2020-03-26 23:11:40
- Tracker changed from Bug to Feature
- Status changed from Confirmed to Needs Validation
- Assignee changed from sajolida to CyrilBrulebois
Hey! I pushed a call for testing in b1b2bdadc4.
You’ve done TONS of work under the hood but I didn’t find much to tell our users appart from “Secure Boot should work now”.
For example, I don’t think that it was worth mentoning the switch from aufs to overlayfs because it might influence many different things that would be very hard for users to relate to this root cause (and we’ll catch the most obvious ones ourselves while dogfooding).
I copied instructions for Mac from my doc/17492-secure-boot.
But it’s good to have me write some of these RC notes from time to time as I can improve bit of the template that is being copie from one call to the other :)
#3 Updated by CyrilBrulebois 2020-03-26 23:23:00
- Assignee changed from CyrilBrulebois to sajolida
Thanks, @sajolida!
You seem to have pushed it to the testing branch, but we’re supposed to be forking the web/release-4.5-rc1 from the master branch since this isn’t a final release. Should I just be cherry-picking your commit on top of master?
(I’m just about to initialize the said branch.)
#4 Updated by CyrilBrulebois 2020-03-26 23:26:06
Ah, and the release process doc contains:
From now on, we don't want to push new commits on `$RELEASE_BRANCH`
until the new release is out. Otherwise, this would break its build
and the build of every branch based on it, which would effectively
block other development work. So the final steps towards publishing
the release will be done in a new, dedicated branch.which is what happened with build #6 → the changelog points at a released version, while we are no longer building from a tag (but one commit further).
I’ll try and remember mentioning to work in a separate branch next time I’m calling for release notes or calls for testing!
#5 Updated by CyrilBrulebois 2020-03-27 18:50:29
- Status changed from Needs Validation to Resolved
- Target version set to Tails_4.5
Merged, thanks!
I had fixed a 4.0 occurrence, but there were some others that I missed, but which were reported by quick users. Fixed in master, hopefully everything’s good again.
The branch dance was done in testing and devel so the extra commit in the wrong place shouldn’t be an issue anymore. Waiting for Jenkins to confirm, and clearly a topic for release managers to handle anyway. ;)