Bug #17361
Streamline our release process
0%
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.
Subtasks
Related issues
| Related to Tails - Bug #17353: .build-manifest discrepancies | In Progress | ||
|
Related to Tails - |
Resolved | ||
|
Related to Tails - |
Resolved | 2018-02-05 | |
|
Related to Tails - |
Resolved | 2014-12-18 | |
|
Related to Tails - |
Resolved | ||
| Related to Tails - Bug #17364: The build of our production website should be self-healing | Confirmed | ||
|
Related to Tails - |
Resolved | ||
| Related to Tails - Bug #16960: Make our CI feedback loop shorter | In Progress | ||
|
Related to Tails - |
Resolved | ||
| Related to Tails - Bug #17413: Document process for emergency releases | Confirmed | ||
|
Related to Tails - |
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 - |
Resolved | ||
|
Related to Tails - |
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 - |
Resolved | ||
| Related to Tails - Bug #17577: Release process: document (changelog) merging | Confirmed | ||
| Related to Tails - Bug #17578: Release process: document setting version manually | Confirmed | ||
| Related to Tails - Feature #17589: Automate post-release GitLab updates | Confirmed |
History
#1 Updated by intrigeri 2019-12-17 11:53:53
- related to Bug #17353: .build-manifest discrepancies added
#2 Updated by intrigeri 2019-12-17 12:00:56
- related to
Bug #17307: nginx "504 Gateway Time-out" while refreshing the website at Tails release time added
#3 Updated by intrigeri 2019-12-17 12:01:58
- related to
Feature #15287: Make it possible to reproducibly generate IUKs in CI added
#4 Updated by intrigeri 2019-12-17 12:02:36
- related to
Feature #8415: Migrate from aufs to overlayfs added
#5 Updated by intrigeri 2019-12-17 12:09:50
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 2019-12-18 11:45:54
- related to
Bug #17363: Ensure only pushes to the master branch trigger a website refresh added
#7 Updated by intrigeri 2019-12-18 11:53:52
- related to Bug #17364: The build of our production website should be self-healing added
#8 Updated by intrigeri 2019-12-26 17:45:11
- related to
Bug #17376: Complete our release process doc wrt. non-final releases added
#9 Updated by intrigeri 2019-12-27 13:37:39
- related to Bug #16960: Make our CI feedback loop shorter added
#10 Updated by intrigeri 2020-01-05 19:05:33
- related to
Feature #17400: Use the tarball with all Tor Browser langpacks added
#11 Updated by intrigeri 2020-01-09 12:50:07
- related to Bug #17413: Document process for emergency releases added
#12 Updated by intrigeri 2020-01-11 10:00:04
- related to
Bug #17420: test channel: consider copying UDF for $VERSION as well added
#13 Updated by intrigeri 2020-01-11 10:00:12
- related to Bug #17414: Slow networking for release management added
#14 Updated by intrigeri 2020-01-11 10:00:20
- related to Bug #17417: Please adjust ISO history handling (git hook?) added
#15 Updated by intrigeri 2020-01-12 19:40:48
- related to
Bug #17431: Consider dropping the latest release version and date from the website sidebar added
#16 Updated by intrigeri 2020-01-13 08:06:12
- related to
Bug #17416: Create a Schleuder mailing list for manual testers added
#17 Updated by intrigeri 2020-01-13 08:50:12
- related to Bug #17434: Building many IUKs (v2) takes a while on Jenkins added
#18 Updated by intrigeri 2020-01-13 08:50:34
- related to Bug #17435: Building many IUKs (v2) takes a while on the RM's system added
#19 Updated by intrigeri 2020-01-14 08:20:11
- related to
Bug #17437: Check which 4.x base versions we need to support upgrades for added
#20 Updated by intrigeri 2020-04-01 07:33:25
- related to Bug #17577: Release process: document (changelog) merging added
#21 Updated by intrigeri 2020-04-01 07:33:48
- related to Bug #17578: Release process: document setting version manually added
#22 Updated by intrigeri 2020-04-04 18:10:14
- related to Feature #17589: Automate post-release GitLab updates added