Bug #16241

release_process: consider dropping the sid-only warning for IUK/upgrade-description

Added by CyrilBrulebois 2018-12-22 23:12:08 . Updated 2019-08-30 20:48:59 .

Status:
Resolved
Priority:
Normal
Assignee:
CyrilBrulebois
Category:
Target version:
Start date:
2018-12-22
Due date:
% Done:

0%

Feature Branch:
Type of work:
Contributors documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

Tools work just fine on stretch as evidenced by my releasing 3.10, 3.10.1, and 3.11, so let’s remove this warning entirely?

Tentative patch attached.


Files


Subtasks


History

#1 Updated by mercedes508 2018-12-23 17:16:32

  • Status changed from New to Confirmed

#2 Updated by intrigeri 2019-01-02 18:15:58

  • Status changed from Confirmed to In Progress

Applied in changeset commit:tails|87a05a1b1fac4a673abdea939db4dc2416f69db0.

#3 Updated by intrigeri 2019-01-02 18:19:10

  • Assignee set to CyrilBrulebois
  • QA Check set to Ready for QA

Hi,

> Tools work just fine on stretch as evidenced by my releasing 3.10, 3.10.1, and 3.11, so let’s remove this warning entirely?

I’d rather not: there’s historically been quite some bad feelings (mostly on anonym’s side) about difficulties to run these tools in various environments. IIRC that’s why this warning was added in the first place. The fact the tools currently work on Stretch don’t guarantee they will still work on Stretch in 2 months, nor on Buster in a year. So I’d rather keep something in place.

But I agree the current phrasing is too vague, does not reflect currently reality, and does not explain well why things might break on stable. I’ve tried to improve this with commit:87a05a1b1fac4a673abdea939db4dc2416f69db0. What do you think?

#4 Updated by intrigeri 2019-06-02 14:42:57

  • Status changed from In Progress to Needs Validation

#5 Updated by intrigeri 2019-08-30 20:48:59

  • Status changed from Needs Validation to Resolved

I believe I have addressed the concerns this ticket was about. Please reopen if that’s not the case!