[Bug 1630040] Re: [SRU] update to 1.0.42
** Description changed: This is a collective tracking bug for snap-confine SRU to version 1.0.42 as released in yakkety. [Impact] The release includes multiple changes. For details see all the bugs on the following milestones: + https://launchpad.net/snap-confine/trunk/1.0.43 https://launchpad.net/snap-confine/trunk/1.0.42 https://launchpad.net/snap-confine/trunk/1.0.41 https://launchpad.net/snap-confine/trunk/1.0.40 https://launchpad.net/snap-confine/trunk/1.0.39 Because of the way SRUs were handled before many of those bugs are currently fixed in xenial (they were added as patches to the .38 version that is released there now. Most of the bugs there have SRU meta-data (except for milestone .42). Please consult individual bugs for detailed impact assessment. Overall the impact is major as some new features are included but they were tested in yakkety as well as in the extensive snap testing machinery (both snapd and snap-confine include multiple spread tests) [Test Case] Likewise test cases are attached to individual bugs. Please make note of the fact that test case are always designed to run as root (this is not stated explicitly in other places). [Regression Potential] See impact. This was tested heavily in spread but there might be edge cases we've missed. The most important change is the introduction of namespace sharing for the mount namespace. This is described in depth here: https://bugs.launchpad.net/snappy/+bug/1611444 [Other Info] Snap-confine is a part of snapd which is under special exception to allow new features in SRUs. For more details please see https://wiki.ubuntu.com/SnapdUpdates ** Summary changed: - [SRU] update to 1.0.42 + [SRU] update to 1.0.43 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630040 Title: [SRU] update to 1.0.43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1630040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630040] Re: [SRU] update to 1.0.42
Hello Jamie, or anyone else affected, Accepted snap-confine into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/snap- confine/1.0.42-0ubuntu3~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: snap-confine (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630040 Title: [SRU] update to 1.0.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1630040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630040] Re: [SRU] update to 1.0.42
** Description changed: - TODO: + This is a collective tracking bug for snap-confine SRU to version 1.0.42 + as released in yakkety. [Impact] - * An explanation of the effects of the bug on users and + The release includes multiple changes. For details see all the bugs on + the following milestones: - * justification for backporting the fix to the stable release. + https://launchpad.net/snap-confine/trunk/1.0.42 + https://launchpad.net/snap-confine/trunk/1.0.41 + https://launchpad.net/snap-confine/trunk/1.0.40 + https://launchpad.net/snap-confine/trunk/1.0.39 - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + Because of the way SRUs were handled before many of those bugs are + currently fixed in xenial (they were added as patches to the .38 version + that is released there now. + + Most of the bugs there have SRU meta-data (except for milestone .42). + Please consult individual bugs for detailed impact assessment. Overall + the impact is major as some new features are included but they were + tested in yakkety as well as in the extensive snap testing machinery + (both snapd and snap-confine include multiple spread tests) [Test Case] - * detailed instructions how to reproduce the bug - - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + Likewise test cases are attached to individual bugs. Please make note of + the fact that test case are always designed to run as root (this is not + stated explicitly in other places). [Regression Potential] - * discussion of how regressions are most likely to manifest as a result - of this change. + See impact. This was tested heavily in spread but there might be edge + cases we've missed. The most important change is the introduction of + namespace sharing for the mount namespace. This is described in depth + here: - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + https://bugs.launchpad.net/snappy/+bug/1611444 [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + Snap-confine is a part of snapd which is under special exception to + allow new features in SRUs. Please see individual bugs for details. ** Description changed: This is a collective tracking bug for snap-confine SRU to version 1.0.42 as released in yakkety. [Impact] The release includes multiple changes. For details see all the bugs on the following milestones: https://launchpad.net/snap-confine/trunk/1.0.42 https://launchpad.net/snap-confine/trunk/1.0.41 https://launchpad.net/snap-confine/trunk/1.0.40 https://launchpad.net/snap-confine/trunk/1.0.39 Because of the way SRUs were handled before many of those bugs are currently fixed in xenial (they were added as patches to the .38 version that is released there now. Most of the bugs there have SRU meta-data (except for milestone .42). Please consult individual bugs for detailed impact assessment. Overall the impact is major as some new features are included but they were tested in yakkety as well as in the extensive snap testing machinery (both snapd and snap-confine include multiple spread tests) [Test Case] Likewise test cases are attached to individual bugs. Please make note of the fact that test case are always designed to run as root (this is not stated explicitly in other places). [Regression Potential] See impact. This was tested heavily in spread but there might be edge cases we've missed. The most important change is the introduction of namespace sharing for the mount namespace. This is described in depth here: https://bugs.launchpad.net/snappy/+bug/1611444 [Other Info] Snap-confine is a part of snapd which is under special exception to - allow new features in SRUs. Please see individual bugs for details. + allow new features in SRUs. + + For more details please see https://wiki.ubuntu.com/SnapdUpdates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630040 Title: [SRU] update to 1.0.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1630040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630040] Re: [SRU] update to 1.0.42
** Description changed: - TODO... + TODO: + + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Case] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + [Regression Potential] + + * discussion of how regressions are most likely to manifest as a result + of this change. + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630040 Title: [SRU] update to 1.0.42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1630040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
