group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1708651@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package maas -
2.2.2-6099-g8751f91-0ubuntu1~17.04.1

---------------
maas (2.2.2-6099-g8751f91-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

  * Stable Release Update. New MAAS upstream release 2.2.2 (LP: #1708651)
    - MAAS 2.2.2 is a new upstream bugfix release that fixes several bugs
      present on MAAS 2.2.0. This is solely a bug fix release. To see what
      issues have been fixes, please refer to the CHANGELOG.
  * debian/control: Conflicts with python3-googleapi.
  * debian/rules: Drop get-orig-source as MAAS & packaging are now in GIT.

 -- Andres Rodriguez <andreserl@xxxxxxxxxx>  Fri, 04 Aug 2017 08:37:54
-0400

** Changed in: maas (Ubuntu Zesty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1708651

Title:
  [SRU] MAAS 2.2.2

Status in maas package in Ubuntu:
  Won't Fix
Status in maas source package in Xenial:
  Fix Released
Status in maas source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  This is a new upstream release that addresses various upstream bugs. MAAS 2.2.2 does NOT introduce any new features.

  Please see CHANGELOG for further details.

  [Test Case]
  MAAS testing has been done in various cases, partially documented https://wiki.ubuntu.com/MAASUpdates. This include:

  All MAAS Upstream releases follow the following testing:

  1. Manual Fresh installation of MAAS
  2. Manual upgrade from the previous Ubuntu Release.
  3. Automated (CI) testing of MAAS install and operation as per the MAAS' CI.
  4. Automated (CI) testing of MAAS install and operation against other Canonical's product (juju, Canonical OpenStack & Kubernetes) provided by the Canonical Solutions QA Team.
  5. Manual split region/rack test are performed. This is to ensure that if we upgrade a MAAS Region to a newer version, the MAAS rack of the older version remains connected and operational.

  Packages from proposed have the following testing to guard against
  misbuilds:

  1. Manual Fresh installation, configuration and deployment of machines.
  2. Manual upgrade from the previous Ubuntu Release (and ensure continued operation)
  3. Includes split region/rack tests.

  All of this includes verifying normal operation, issues fixed, and
  ensuring that Canonical Cloud solutions can inter-operate. MAAS
  releases are also now vetted by the Solutions QA team.

  [Regression Potential]
  Minimal (For MAAS itself). MAAS 2.2.2 is just a point release that addresses bugs and does not change any behavior. It has minimum risk for backward compatibility issues. It does NOT include any database migrations as such, upgrade risks are very minimal as well.

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