** Description changed: I would like to request a general approval to backport the current development series of https://launchpad.net/ubuntu/+source/cockpit to Ubuntu 16.04 LTS. Reason ====== http://cockpit-project.org/ is a web equivalent of a desktop, for managing a (small) number of local machines (desktops or servers). Please see http://cockpit-project.org/ for details. Upstream primarily targets servers, thus the real aim for this project is the LTSes. Current Ubuntu Cockpit users consume it from https://launchpad.net /~cockpit-project/+archive/ubuntu/cockpit (which is subject to the same automated testing and release process), but it would be nice to make it available in the official backports, as well as for all of Ubuntu's supported architectures. + See https://piware.de/post/2017-05-09-cockpit-in-debian-ubuntu/ for a + general intro and motivation. + Testing ======= Upstream has a very comprehensive unit and integration test suite; the latter runs on lots of OSes, amongst them are Ubuntu 16.04 LTS, Debian 8 (Jessie) and Debian testing. (Example: https://github.com/cockpit-project/cockpit/pull/6376). As such *every* change in master gets verified that it builds, installs, and correctly works in Ubuntu 16.04 LTS, so testing there is much more thorough than for Ubuntu development series (where I just do some manual testing of the upstream releases). Reverse dependencies ==================== Cockpit is (currently) a leaf project without reverse dependencies. In the future the intention is that various services can ship/provide their own Cockpit module to integrate into the web UI. There is a stable module interface and communication protocol, but there are no current plans yet how to do CI across these project boundaries. Once that becomes an issue, this will be discussed upstream. Presumably this will involve the usual automatic reverse dependency autopkgtesting that we do for all packages in Ubuntu. Process ======= The cockpit package as in Ubuntu zesty and devel backport and work without any changes on Ubuntu 16.04; just "backportpackage" is sufficient. I would like to handle this myself (uploading and queue processing), but I'd like to get a formal ack on this first.
** Description changed: I would like to request a general approval to backport the current development series of https://launchpad.net/ubuntu/+source/cockpit to Ubuntu 16.04 LTS. Reason ====== http://cockpit-project.org/ is a web equivalent of a desktop, for managing a (small) number of local machines (desktops or servers). Please see http://cockpit-project.org/ for details. Upstream primarily targets servers, thus the real aim for this project is the LTSes. Current Ubuntu Cockpit users consume it from https://launchpad.net /~cockpit-project/+archive/ubuntu/cockpit (which is subject to the same automated testing and release process), but it would be nice to make it available in the official backports, as well as for all of Ubuntu's supported architectures. See https://piware.de/post/2017-05-09-cockpit-in-debian-ubuntu/ for a general intro and motivation. Testing ======= - Upstream has a very comprehensive unit and integration test suite; the latter runs on lots of OSes, amongst them are Ubuntu 16.04 LTS, Debian 8 (Jessie) and Debian testing. (Example: https://github.com/cockpit-project/cockpit/pull/6376). As such *every* change in master gets verified that it builds, installs, and correctly works in Ubuntu 16.04 LTS, so testing there is much more thorough than for Ubuntu development series (where I just do some manual testing of the upstream releases). + Upstream has a very comprehensive unit and integration test suite; the latter runs on lots of OSes, amongst them are Ubuntu 16.04 LTS, Debian 8 (Jessie) and Debian testing. (Example: https://github.com/cockpit-project/cockpit/pull/6376). As such *every* change in master gets verified that it builds, installs, and correctly works in Ubuntu 16.04 LTS, so testing there is much more thorough than for Ubuntu development series (where I just do some manual testing of the upstream releases, and of course there's the unit tests and autopkgtests which run part of upstream's tests). Reverse dependencies ==================== Cockpit is (currently) a leaf project without reverse dependencies. In the future the intention is that various services can ship/provide their own Cockpit module to integrate into the web UI. There is a stable module interface and communication protocol, but there are no current plans yet how to do CI across these project boundaries. Once that becomes an issue, this will be discussed upstream. Presumably this will involve the usual automatic reverse dependency autopkgtesting that we do for all packages in Ubuntu. Process ======= The cockpit package as in Ubuntu zesty and devel backport and work without any changes on Ubuntu 16.04; just "backportpackage" is sufficient. I would like to handle this myself (uploading and queue processing), but I'd like to get a formal ack on this first. -- You received this bug notification because you are a member of Ubuntu Backporters, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1686022 Title: Please backport cockpit 138-1 and future versions from devel To manage notifications about this bug go to: https://bugs.launchpad.net/xenial-backports/+bug/1686022/+subscriptions -- ubuntu-backports mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
