** Description changed: [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 of MAAS + 2. Manual upgrade from the previous Ubuntu Release. + 3. Manual 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.
** Description changed: [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 of MAAS - 2. Manual upgrade from the previous Ubuntu Release. - 3. Manual split region/rack tests. + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708651 Title: [SRU] MAAS 2.2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1708651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
