Anthony Towns <aj@azure.humbug.org.au> writes: > Generally, experimental fits the above role. Unstable's for uploading new > development of packages that will hopefully work, but might turn out not > to. In particular, though, they need to be fixed pretty quickly -- six > months in experimental, and another two so far in unstable isn't quickly.
So can you explain for me when this policy change was made and where it was announced? I must have missed it. I refer specifically to the statement that if a package in unstable does not work, in needs to be fixed "pretty quickly". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
