Hi Matej, Matej Cepl <[EMAIL PROTECTED]> writes: > Hi, > > the problem is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=316626 -- it > is one of those "last minute before freezing stable" uploads and it went > horribly wrong, resulting that current Debian/stable has non-functional > package. I tried to persuade Joey, that vim-vimoutliner should go to > stable-proposed-updates, but he rejected me, because VO didn't seem to be > important enough for him. However, number of grumbling users of stable > Debian is getting higher, so I would like to ask once more -- could the > current vim-vimoutliner from testing go to stable-updates? There has not > been a big bugs for a long time (currently, there is no open bug (I forgot > to close #383694).
Stable update policy is as follows: 1. The package fixes a security problem. An advisory by our own Security Team is required. Updates need to be approved by the Security Team. 2. The package fixes a critical bug which can lead to data loss, data corruption, or an overly broken system, or the package is broken. 3. The stable version of the package is not installable at all due to broken or unmet dependencies or broken installation scripts. 4. All released architectures have to be in sync. 5. The package gets all released architectures back in sync. I don't see any of above criteria matched here. Okay, one could argue about 2 here (the package is broken), but i don't see a reason ATM to fix a normal bug in the next point release. So no, i don't see this this as a valid candidate. Sorry. Greetings Martin -- Martin Zobel-Helas GPG Key-ID: 0x5d64f870 Debian Developer eMail Privat: [EMAIL PROTECTED] Debian Stable Release Manager eMail Debian: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
