On Tue, Dec 17, 2013 at 6:16 PM, Dmitry Smirnov <only...@debian.org> wrote: > Hi Scott, > > For your information I have a case that you might find interesting: > > Zabbix did not meet release criteria and was removed from "testing" > just before release of Wheezy. Ever since yours truly was maintaining > it in wheezy-backports. > > Why wouldn't we seek backports manager(s)' permission to provide > "bitcoin" in wheezy-backports?
Sorry for long delay, just saw this. This sounds good., it will give us the control to prevent stable release with the flexibility of constant updates. Users will have to enable backports, and thus know and be willing to keep the package up to date. I think it's crucial that we have several people working to keep the package up to date in backports, since it will not be automatic. There is more work, but I think this fits all the requirements upstream wants (flexibility of updating) with the way things work in Debian. We'd keep this bug open to prevent transition to stable, but maintain the package in unstable and backports directly. If someone wants to work and backport and maintain bticoin in backports, long-term, I think that's a good idea. It might be more responsibility than I can take on at the moment, however. ~Scott -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
