[Bug 2098750] [NEW] [MIR] automake-1.17 re-review

Lukas Märdian 2098750 at bugs.launchpad.net
Tue Feb 18 11:31:51 UTC 2025


Public bug reported:

Automake in "main" moved from automake-1.16 to automake-1.17 during the
Plucky development cycle.

I was unable to find any (old) MIR for automake.

According to [0] we want to catch such occasions and do and opt-in MIR
review for packages that did not receive such review in the recent past
(or at all), in order to improve quality of those packages.


Such review is not to block the promotion of the automake-1.16 -> automake-1.17 rename, but should hopefully lead to some actionable suggestions of how the package can be improved going forward, based upon the MIR best-practices.

There will be no "Required TODOs", but any suggestion should be
considered optional/Recommended.


Would the Foundations team be interested in filing such MIR for automake-1.17, using the normal template [1] and re-using this bug report?

[0] https://github.com/canonical/ubuntu-mir#re-reviews
[1] https://github.com/canonical/ubuntu-mir#main-inclusion-requirements

** Affects: automake-1.17 (Ubuntu)
     Importance: Low
         Status: Incomplete


** Tags: plucky rls-pp-incoming

** Summary changed:

- [MIR] automake-1.17
+ [MIR] automake-1.17 re-review

** Tags added: rls-pp-incoming

** Changed in: automake-1.17 (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to automake-1.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2098750

Title:
  [MIR] automake-1.17 re-review

Status in automake-1.17 package in Ubuntu:
  Incomplete

Bug description:
  Automake in "main" moved from automake-1.16 to automake-1.17 during
  the Plucky development cycle.

  I was unable to find any (old) MIR for automake.

  According to [0] we want to catch such occasions and do and opt-in MIR
  review for packages that did not receive such review in the recent
  past (or at all), in order to improve quality of those packages.

  
  Such review is not to block the promotion of the automake-1.16 -> automake-1.17 rename, but should hopefully lead to some actionable suggestions of how the package can be improved going forward, based upon the MIR best-practices.

  There will be no "Required TODOs", but any suggestion should be
  considered optional/Recommended.

  
  Would the Foundations team be interested in filing such MIR for automake-1.17, using the normal template [1] and re-using this bug report?

  [0] https://github.com/canonical/ubuntu-mir#re-reviews
  [1] https://github.com/canonical/ubuntu-mir#main-inclusion-requirements

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automake-1.17/+bug/2098750/+subscriptions




More information about the foundations-bugs mailing list