Re: Why no Opera?
That is, all software that makes it to into testing should be
stable and release quality and ready for testing with *the rest of the
packages slated for the next release*.
Ok. In the event of a piece of software which is likely to need little
testing and be updated upstream several times between releases (such
as Opera) how would this best be handled? Should one wait until a few
month prior to the next release instead of repackaging it and sending
it back through the various releases multiple times between Debian
"Everything should be made as simple as possible, but not simpler."