Howdy folks, I'm sending to both -devel and backports. I'm not sure which is the correct list. If one's wrong, feel free to drop it in replies.
I've been talking with a mentee about backporting procedures, and I've explained why we don't backport until a package hits tending (stable < stable-bpo < testing <= unstable) However, with the new testing removals from the release team (which is totally great for creating an always releasable testing, many thanks for that), we can create a situation where stable-bpo has a newer version than testing when we release (lazy maintainer never fixed the rc bug). What shall we do? Remove from stable-bpo? Hope an update comes around? Does it make sense to revisit the rules? Does a wait until testing still make sense (ok, waiting always makes sense, but beyond the 'let it settle' thing) Much love, Paul -- .''`. Paul Tagliamonte <paul...@debian.org> | Proud Debian Developer : :' : 4096R / 8F04 9AD8 2C92 066C 7352 D28A 7B58 5B30 807C 2A87 `. `'` http://people.debian.org/~paultag `- http://people.debian.org/~paultag/conduct-statement.txt
signature.asc
Description: Digital signature
