Project

General

Profile

Bug #17361

Streamline our release process

Added by intrigeri 2 months ago. Updated 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

It's not clear yet how we'll approach this streamlining thing, but in the meantime, I feel the need to have a place to collect a list of specific issues we're facing as part of doing releases. This should help us get a better understanding of the big picture, prioritize issues relatively to each other, and get a better idea of what kind of efforts would yield what kind of benefits.

I propose we simply mark candidate issues as Related to this one for now. The ones we pick as higher priority could become subtasks later.


Related issues

Related to Tails - Bug #17353: .build-manifest discrepancies In Progress
Related to Tails - Bug #17307: nginx "504 Gateway Time-out" while refreshing the website at Tails release time Needs Validation
Related to Tails - Feature #15287: Make it possible to reproducibly generate IUKs in CI Resolved 02/05/2018
Related to Tails - Feature #8415: Migrate from aufs to overlayfs In Progress 12/18/2014
Related to Tails - Bug #17363: Ensure only pushes to the master branch trigger a website refresh Resolved
Related to Tails - Bug #17364: The build of our production website should be self-healing Confirmed
Related to Tails - Bug #17376: Complete our release process doc wrt. non-final releases Confirmed
Related to Tails - Bug #16960: Make our CI feedback loop shorter Confirmed
Related to Tails - Feature #17400: Use the tarball with all Tor Browser langpacks Resolved
Related to Tails - Bug #17413: Document process for emergency releases Confirmed
Related to Tails - Bug #17420: test channel: consider copying UDF for $VERSION as well Resolved
Related to Tails - Bug #17414: Slow networking for release management Confirmed
Related to Tails - Bug #17417: Please adjust ISO history handling (git hook?) Confirmed
Related to Tails - Bug #17431: Consider dropping the latest release version and date from the website sidebar Confirmed
Related to Tails - Bug #17416: Create a Schleuder mailing list for manual testers Resolved
Related to Tails - Bug #17434: Building many IUKs (v2) takes a while on Jenkins Confirmed
Related to Tails - Bug #17435: Building many IUKs (v2) takes a while on the RM's system Confirmed
Related to Tails - Bug #17437: Check which 4.x base versions we need to support upgrades for Confirmed

History

#1 Updated by intrigeri 2 months ago

  • Related to Bug #17353: .build-manifest discrepancies added

#2 Updated by intrigeri 2 months ago

  • Related to Bug #17307: nginx "504 Gateway Time-out" while refreshing the website at Tails release time added

#3 Updated by intrigeri 2 months ago

  • Related to Feature #15287: Make it possible to reproducibly generate IUKs in CI added

#4 Updated by intrigeri 2 months ago

#5 Updated by intrigeri 2 months ago

For now I'm not linking issues that affect RMs just like they affect developers, such as those pertaining to fragility of our build system, or of our test suite, or of our test suite specifically on lizard.

Some recent discussions with segfault make me wish we went through a similar process from the perspective of a Tails developer. For now I'd rather not conflate these 2 processes, but it would be good to keep in mind that fixing such issues would not only make life better for RMs, but also for all other developers, which can give them a strong advantage, compared to release process -only improvements, in terms of cost/benefit.

Anyway, we have a meeting about this in 10 days so I won't think about it further now.

#6 Updated by intrigeri 2 months ago

  • Related to Bug #17363: Ensure only pushes to the master branch trigger a website refresh added

#7 Updated by intrigeri 2 months ago

  • Related to Bug #17364: The build of our production website should be self-healing added

#8 Updated by intrigeri about 2 months ago

  • Related to Bug #17376: Complete our release process doc wrt. non-final releases added

#9 Updated by intrigeri about 2 months ago

  • Related to Bug #16960: Make our CI feedback loop shorter added

#10 Updated by intrigeri about 2 months ago

  • Related to Feature #17400: Use the tarball with all Tor Browser langpacks added

#11 Updated by intrigeri about 1 month ago

  • Related to Bug #17413: Document process for emergency releases added

#12 Updated by intrigeri about 1 month ago

  • Related to Bug #17420: test channel: consider copying UDF for $VERSION as well added

#13 Updated by intrigeri about 1 month ago

  • Related to Bug #17414: Slow networking for release management added

#14 Updated by intrigeri about 1 month ago

  • Related to Bug #17417: Please adjust ISO history handling (git hook?) added

#15 Updated by intrigeri about 1 month ago

  • Related to Bug #17431: Consider dropping the latest release version and date from the website sidebar added

#16 Updated by intrigeri about 1 month ago

  • Related to Bug #17416: Create a Schleuder mailing list for manual testers added

#17 Updated by intrigeri about 1 month ago

  • Related to Bug #17434: Building many IUKs (v2) takes a while on Jenkins added

#18 Updated by intrigeri about 1 month ago

  • Related to Bug #17435: Building many IUKs (v2) takes a while on the RM's system added

#19 Updated by intrigeri about 1 month ago

  • Related to Bug #17437: Check which 4.x base versions we need to support upgrades for added

Also available in: Atom PDF