Tails

#1 Updated by intrigeri 2019-06-18 18:13:19

Current plan: release this at the same time as 3.15, on 2019-07-09. I’ve assigned myself as a fallback for the RM’ing work, but I certainly would not mind if anonym took this over, especially since it’s not 100% clear yet whether kibi will be in a position to RM 3.15 in the end.

For now, we’re tracking the blockers as 4.0 tickets with priority >> normal. We’ll see how it works.

sajolida, I think we’ll need a dedicated blog post + tweet, to give this more exposure than a mere call for testing on -testers@.

#3 Updated by intrigeri 2019-06-18 18:18:41

intrigeri wrote:
> Current plan: release this at the same time as 3.15, on 2019-07-09. I’ve assigned myself as a fallback for the RM’ing work, but I certainly would not mind if anonym took this over, especially since it’s not 100% clear yet whether kibi will be in a position to RM 3.15 in the end.

Actually, we don’t have to release this at the same time as 3.15: any time in the following week or so would work. But if I need to be involved, 2019-07-09 works best: I’ll be mostly unavailable after that.

#4 Updated by intrigeri 2019-07-05 16:07:49

Emailed the RMs list, trying to figure out who can do that and when.

#6 Updated by sajolida 2019-07-31 17:21:25

I’m fine helping with the announcement but I think it’ll be better if you help me draft what I should mention:

• How to test: anything special?
• What’s new: will I have all the info in the Changelog already?
• Known issues

You can have a look at the announcement of 3.0-beta4 to have a point of comparison.

#9 Updated by intrigeri 2019-08-05 11:42:02

sajolida wrote:
> * How to test: anything special?

One thing: we stopped forcing the “intel” X.Org driver for a bunch of graphic cards (Feature #14991). In the earlier calls for testing of feature/buster I’ve asked folks using such hardware to report success/failure. If they experience a regression they should retry with xorg-driver=intel. In any case, it’s nice if they report the ID of the graphic card.

Also, again, same as earlier calls for testing: Thunderbold testing would be sweet. I provided more detailed instructions in those calls for testing.

#10 Updated by anonym 2019-08-05 19:09:12

sajolida wrote:
> I’m fine helping with the announcement

I have taken this over and plan to start working on it ASAP. @sajolida, do you think you have time to write it by 16:00 CEST Aug 7? Or even earlier?

> * What’s new: will I have all the info in the Changelog already?

I can reorder the release process a bit and just prepare the changelog first thing tomorrow morning.

#11 Updated by anonym 2019-08-06 13:09:13

sajolida, a WIP changelog has been pushed to feature/buster! It’s huge, but not so crazy when looking at the sections relevant for you:

• Major changes
• Removed features
• Bugfixes
• Minor improvements and updates

Please ignore the other sections! (If you happen to find anything relevant in the “Adjustments for Debian 10” section, please let me know, cause then I should probably move it to “Minor improvements”.)

#12 Updated by anonym 2019-08-06 13:13:03

@sajolida, my mention of you got broken in my previous post, so doing it in this post instead.

#13 Updated by sajolida 2019-08-06 17:23:14

The last proposed date was 2019-07-09 which was silently postponed until yesterday, so being given only a 48 hours notice is pretty rough.

Today I was not working on Tails until now and tomorrow I have 2 important fundraising meetings. I’ll start working on the note right now but I can’t promise you anything.

#14 Updated by sajolida 2019-08-06 17:35:22

I’ll need URLs to the images and OpenPGP signatures.

#15 Updated by sajolida 2019-08-06 19:22:47

I pushed a draft to doc/16822-4.0-beta1.

I didn’t mention anything related to Electrum on purpose because I understand that it’s still unusable in the general case.

You can probably finish it yourself by linking to the image and OpenPGP signature whenever it’s ready. I don’t mind doing it myself but I cannot promise highly availability.

#16 Updated by anonym 2019-08-07 08:11:35

sajolida wrote:
> The last proposed date was 2019-07-09 which was silently postponed until yesterday, so being given only a 48 hours notice is pretty rough.

Fully understood, but I couldn’t have let you know any earlier. However, I should have made it clearer that the proposed deadline could be discussed in case you needed a day or two more. Sorry!

> I pushed a draft to doc/16822-4.0-beta1.

Thanks a lot!

> I didn’t mention anything related to Electrum on purpose because I understand that it’s still unusable in the general case.

Yes, it’s still unusable.

> You can probably finish it yourself by linking to the image and OpenPGP signature whenever it’s ready. I don’t mind doing it myself but I cannot promise highly availability.

I’ll do it, np!