Hi, Nick Andrik wrote (12 Dec 2012 15:18:54 GMT) : > 2012/12/12 intrigeri <intrig...@debian.org>: >> OK. I think the key question then becomes: as the upcoming maintainer >> of kismet in Debian, do you want to commit to maintain 2008-05-R1-4.3 >> in stable once Wheezy is released? (as in: dealing with security >> issues, fixing RC bugs through stable updates, answering bug >> reports, etc.)
> If there are any bugs reported on functionality (which I doubt) then > it makes no sense trying to fix the 2008 version. > All other bugs are OK. I'm not sure I understand what you mean by "bugs reported on functionality". If you mean "feature requests", then they are not appropriate for packages shipped in a stable release, so indeed it does not make sense, and then I gather your answer was a "yes". If you mean anything else, please clarify :) FYI, the stable suite update policy can be found on the Release Team homepage [1]. [1] http://release.debian.org/ > BTW, I guess there is no chance to have the new package in wheezy once > it gets released, is this correct? This is correct. The current freeze policy can be read there: http://release.debian.org/wheezy/freeze_policy.html > If we need to fix anything then I will have to keep different > branches, i.e. one for stable and one for testing, right? This is indeed one common way to organize your packaging VCS. In any case, please refrain from pushing to unstable stuff that is not meant for Wheezy, until it is released. You'll rather want to push to experimental in the meantime. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
