Public bug reported: https://github.com/canonical/regress-stack/ is a new project with goal to improve regression testing in ubuntu packages.
It is an opinionated installation of a single node OpenStack meant to run inside an autopkgtest runner. The goal is for this package's functional testing to be run whenever a dependency is updated, and help catch errors in packages much earlier. Since this would be a new package, it does not fall under the FeatureFreeze exception: > FeatureFreeze for new packages >New source packages in the archive do not require feature freeze exceptions, as they must be explicitly opted into by users. For NEW uploads which are not syncs from Debian, please make sure you have the agreement of a member of ~ubuntu-archive to perform the necessary queue reviews before you upload. >However, at the point where you integrate the new package into an existing one (e.g. adding a dependency or turning on a feature) or add it to a seed, feature freeze begins to apply and you must seek an exception. This is the point at which risk is added to people who didn't explicitly choose it. AMD64 build of the package: https://launchpad.net/~gboutry/+archive/ubuntu/regress- stack/+build/30421493 ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: https://github.com/canonical/regress-stack/ is a new project with goal to improve regression testing in ubuntu packages. It is an opinionated installation of a single node OpenStack meant to run inside an autopkgtest runner. The goal is for this package's functional testing to be run whenever a dependency is updated, and help catch errors in packages much earlier. Since this would be a new package, it does not fall under the FeatureFreeze exception: > FeatureFreeze for new packages - New source packages in the archive do not require feature freeze - exceptions, as they must be explicitly opted into by users. For NEW - uploads which are not syncs from Debian, please make sure you have the - agreement of a member of ~ubuntu-archive to perform the necessary queue + >New source packages in the archive do not require feature freeze + exceptions, as >they must be explicitly opted into by users. For NEW + uploads which are not >syncs from Debian, please make sure you have the + agreement of a member of >~ubuntu-archive to perform the necessary queue reviews before you upload. - However, at the point where you integrate the new package into an - existing one (e.g. adding a dependency or turning on a feature) or add - it to a seed, feature freeze begins to apply and you must seek an - exception. This is the point at which risk is added to people who didn't - explicitly choose it. + >However, at the point where you integrate the new package into an + existing one >(e.g. adding a dependency or turning on a feature) or add + it to a seed, feature >freeze begins to apply and you must seek an + exception. This is the point at >which risk is added to people who + didn't explicitly choose it. - - AMD64 build of the package: https://launchpad.net/~gboutry/+archive/ubuntu/regress-stack/+build/30421493 + AMD64 build of the package: + https://launchpad.net/~gboutry/+archive/ubuntu/regress- + stack/+build/30421493 ** Description changed: https://github.com/canonical/regress-stack/ is a new project with goal to improve regression testing in ubuntu packages. It is an opinionated installation of a single node OpenStack meant to run inside an autopkgtest runner. The goal is for this package's functional testing to be run whenever a dependency is updated, and help catch errors in packages much earlier. Since this would be a new package, it does not fall under the FeatureFreeze exception: > FeatureFreeze for new packages >New source packages in the archive do not require feature freeze - exceptions, as >they must be explicitly opted into by users. For NEW - uploads which are not >syncs from Debian, please make sure you have the - agreement of a member of >~ubuntu-archive to perform the necessary queue + exceptions, as they must be explicitly opted into by users. For NEW + uploads which are not syncs from Debian, please make sure you have the + agreement of a member of ~ubuntu-archive to perform the necessary queue reviews before you upload. >However, at the point where you integrate the new package into an - existing one >(e.g. adding a dependency or turning on a feature) or add - it to a seed, feature >freeze begins to apply and you must seek an - exception. This is the point at >which risk is added to people who - didn't explicitly choose it. + existing one (e.g. adding a dependency or turning on a feature) or add + it to a seed, feature freeze begins to apply and you must seek an + exception. This is the point at which risk is added to people who didn't + explicitly choose it. AMD64 build of the package: https://launchpad.net/~gboutry/+archive/ubuntu/regress- stack/+build/30421493 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103443 Title: [FFE] upload Regress-Stack to plucky To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2103443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
