Bug #12446

Write release notes for 2.12

Added by sajolida 2017-04-14 11:34:13 . Updated 2017-05-22 17:14:24 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_2.12
Start date:
2017-04-14
Due date:
% Done:

100%

Feature Branch:
doc/12446-2.12-release-notes
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Subtasks

Related issues

Blocks Tails - Feature #12432: Technical writing core work 2017Q2 Resolved 2017-04-07

History

#1 Updated by sajolida 2017-04-14 11:34:26

#2 Updated by sajolida 2017-04-14 14:42:43

  • Status changed from Confirmed to In Progress
  • Feature Branch set to doc/12446-2.12-release-notes

#3 Updated by sajolida 2017-04-14 15:12:39

  • Assignee changed from sajolida to intrigeri
  • QA Check set to Ready for QA

I’m done.

intrigeri: Please check the note I put for you in the What’s coming up? section.

#4 Updated by intrigeri 2017-04-15 08:03:16

  • Assignee changed from intrigeri to sajolida
  • QA Check changed from Ready for QA to Dev Needed

> I’m done.

I’ve found 3 issues:

  • Tails 2.12 will likely ship Linux 4.9.18, not 4.9.0.
  • IMO “If Debian Stretch is released after June 13, our next release will be 2.13” is assuming too much: that’s only true if 1. we are made aware of the Stretch release date (not very likely); and 2. Stretch is planned to be releases no later than July 2.
  • Wrt. “Otherwise, we will try to publish 3.0 before June 13 at the same time as Debian Stretch”: incorrect, see my “Coordinating Debian Stretch & Tails 3.0 releases?” email that should be somewhere in your inbox.

> intrigeri: Please check the note I put for you in the What’s coming up? section.

  • Regarding “the unclear order between beta4 and 2.12”: I will try to announce 3.0~beta4 at the same time as 2.12, but I can’t guarantee anything, so the best I can do is to commit to update the “You can already […]” sentence whenever I publish 3.0~beta4. Good enough?

#5 Updated by sajolida 2017-04-18 19:07:46

> * Tails 2.12 will likely ship Linux 4.9.18, not 4.9.0.

Fixed in both the release notes and the changelog as anonym told me it
was 4.9.13 in the end.

> * IMO “If Debian Stretch is released after June 13, our next release
> will be 2.13” is assuming too much: that’s only true if 1. we are
> made aware of the Stretch release date (not very likely); and 2.
> Stretch is planned to be releases no later than July 2.
>
> * Wrt. “Otherwise, we will try to publish 3.0 before June 13 at the
> same time as Debian Stretch”: incorrect, see my “Coordinating Debian
> Stretch & Tails 3.0 releases?” email that should be somewhere in your
> inbox.

Thanks for pointing our things that were incorrect but I would have
found it more helpful (and prehaps even quicker for both you and me) if
you had also told me what would be correct to write there.

I was trying to be cautious here to be consistent with the ‘?’ in
/contribute/roadmap. But I’m now quite lost in how to deal with that in
an efficient way, so I’ll stick to the intro of your email “Coordinating
Debian Stretch & Tails 3.0 releases?” and announce 3.0 for June 13.
See af432ea335.

I won’t be here tomorrow but feel free to change it to something else if
you want.

> * Regarding “the unclear order between beta4 and 2.12”: I will try to
> announce 3.0~beta4 at the same time as 2.12, but I can’t guarantee
> anything, so the best I can do is to commit to update the “You can
> already […]” sentence whenever I publish 3.0~beta4. Good enough?

Good enough :)

#6 Updated by sajolida 2017-04-18 19:09:23

  • Assignee changed from sajolida to anonym
  • QA Check changed from Dev Needed to Pass

Reassign to anonym for the final merge!

#7 Updated by intrigeri 2017-04-18 20:26:58

sajolida wrote:
> > * Tails 2.12 will likely ship Linux 4.9.18, not 4.9.0.
>
> Fixed in both the release notes and the changelog as anonym told me it
> was 4.9.13 in the end.

Oops, sorry I didn’t notice that we had frozen before 4.9.18 was uploaded to jessie-backports. Too bad.

#8 Updated by anonym 2017-04-19 12:44:11

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 0 to 100

Merged! And I pushed a few corrections and improvements.

#9 Updated by anonym 2017-04-19 17:24:59

  • Status changed from Fix committed to Resolved

#10 Updated by sajolida 2017-05-22 17:14:24

  • QA Check deleted (Pass)