== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
* <TODO: Create list with LP: # included>
See the changelog entry below for a full list of changes and bugs.
In order to avoid regression to existing MAAS product, the MAAS team will
run their continuous integration test against the curtin that is in
-proposed. A successful run will be required before the proposed curtin
can be let into -updates.
The curtin team will be in charge of attaching the artifacts and console
output of the appropriate run to the bug. Curtin team members will not
mark ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.
<TODO: attach curtin-proposed test artifacts from vmtest for every SRU release, not a link as links expire>
<TODO: attach maas-proposed test artifacts from vmtest for every SRU release, not a link as links expire>
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
* <TODO: Create list with LP: # included>
See the changelog entry below for a full list of changes and bugs.
[Test Case] /wiki.ubuntu. com/CurtinUpdat es
The following development and SRU process was followed:
https:/
Curtin now contains an extensive integration test suite that is ran using /curtin. readthedocs. io/en/latest/ topics/ integration- testing. html
the SRU package for each releases. These suite has documentation here:
https:/
In order to avoid regression to existing MAAS product, the MAAS team will
run their continuous integration test against the curtin that is in
-proposed. A successful run will be required before the proposed curtin
can be let into -updates.
The curtin team will be in charge of attaching the artifacts and console
output of the appropriate run to the bug. Curtin team members will not
mark ‘verification-done’ until this has happened.
[Regression Potential]
In order to mitigate the regression potential, the results of the
aforementioned integration tests are attached to this bug.
<TODO: attach curtin-proposed test artifacts from vmtest for every SRU release, not a link as links expire>
<TODO: attach maas-proposed test artifacts from vmtest for every SRU release, not a link as links expire>
[Discussion]
<TODO: other background>
== End SRU Template ==
<TODO: Paste in change log entry>