ubuntustudio-bugs team mailing list archive

[Simon Quigley <1980180@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

(This is starting as a request for comment from the Ubuntu Stable
Release Update Team and will eventually be edited to be an SRU bug.)

In Lubuntu and Ubuntu Studio 22.04 LTS, we dropped the ball by including
the same version of Calamares as we did in 21.10. Upstream considers 3.2
to be an "LTS" series, so we would like to follow the upstream release
cycle to deliver the latest 3.2 point release to our users.

Here is a specific link to the code changes included between the two
versions:
https://github.com/calamares/calamares/compare/v3.2.41.1...v3.2.60

It's quite a lengthy update. As far as I can tell, we have three options:
 A) Update to the latest upstream milestone in 22.04. Go through a thorough test suite, which will be outlined in the SRU bug report, and continue to follow upstream point releases. The benefit of this route is that 3.2.60 has many more eyes on it than 3.2.41.1. Bugs are more easily fixed, and problems are likely to be experienced between multiple distributions, not just us.
 B) We patch 3.2.41.1 with just translations and all bugfixes, only. This will take quite a bit of work to sort through what qualifies as a bugfix, what can be backported, and the rationale for each  bugfix. Would not recommend but perhaps this is the most "standard" option.
 C) Only backport specific high-profile bugfixes to 3.2.41.1.

I'd like to just go with A, and speaking on behalf of Lubuntu I think
that would be the most sustainable option. I'm *very* rusty on this
entire process, so please let me know what other information you may
need to help in processing this request.

Thank you.

** Affects: calamares (Ubuntu)
     Importance: Medium
     Assignee: Simon Quigley (tsimonq2)
         Status: Fix Released

** Affects: calamares (Ubuntu Jammy)
     Importance: Medium
     Assignee: Simon Quigley (tsimonq2)
         Status: New

** Affects: calamares (Ubuntu Kinetic)
     Importance: Medium
     Assignee: Simon Quigley (tsimonq2)
         Status: Fix Released

** Also affects: calamares (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: calamares (Ubuntu Kinetic)
   Importance: Undecided
       Status: New

** Changed in: calamares (Ubuntu Kinetic)
       Status: New => Fix Released

** Changed in: calamares (Ubuntu Kinetic)
   Importance: Undecided => Medium

** Changed in: calamares (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: calamares (Ubuntu Jammy)
     Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: calamares (Ubuntu Kinetic)
     Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: calamares (Ubuntu Jammy)
    Milestone: None => ubuntu-22.04.1

** Changed in: calamares (Ubuntu Kinetic)
    Milestone: None => ubuntu-22.05

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/1980180

Title:
  [SRU] Calamares 3.2 Series for 22.04 LTS

Status in calamares package in Ubuntu:
  Fix Released
Status in calamares source package in Jammy:
  New
Status in calamares source package in Kinetic:
  Fix Released

Bug description:
  (This is starting as a request for comment from the Ubuntu Stable
  Release Update Team and will eventually be edited to be an SRU bug.)

  In Lubuntu and Ubuntu Studio 22.04 LTS, we dropped the ball by
  including the same version of Calamares as we did in 21.10. Upstream
  considers 3.2 to be an "LTS" series, so we would like to follow the
  upstream release cycle to deliver the latest 3.2 point release to our
  users.

  Here is a specific link to the code changes included between the two
  versions:
  https://github.com/calamares/calamares/compare/v3.2.41.1...v3.2.60

  It's quite a lengthy update. As far as I can tell, we have three options:
   A) Update to the latest upstream milestone in 22.04. Go through a thorough test suite, which will be outlined in the SRU bug report, and continue to follow upstream point releases. The benefit of this route is that 3.2.60 has many more eyes on it than 3.2.41.1. Bugs are more easily fixed, and problems are likely to be experienced between multiple distributions, not just us.
   B) We patch 3.2.41.1 with just translations and all bugfixes, only. This will take quite a bit of work to sort through what qualifies as a bugfix, what can be backported, and the rationale for each  bugfix. Would not recommend but perhaps this is the most "standard" option.
   C) Only backport specific high-profile bugfixes to 3.2.41.1.

  I'd like to just go with A, and speaking on behalf of Lubuntu I think
  that would be the most sustainable option. I'm *very* rusty on this
  entire process, so please let me know what other information you may
  need to help in processing this request.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1980180/+subscriptions