On Tue, Mar 12, 2013 at 10:09:59PM +0100, Stephen R. van den Berg wrote:
Which begs another question: why is 7.8.700 not being considered in the first place? I can only imagine that it is a drop-in replacement for 7.8.352 and therefore a nobrainer to update the package.
it wasn't available before the freeze for the next release. after that point updates are only allowed in in exceptional cases which will be carefully reviewed.
dropping in 7.8.700 is not a no-brainer because there might be regressions, and there is no more time to test for them.
and note that just being stable upstream is not good enough, it needs to be verivied to be stable running on debian without breaking anything else.
now for a programming language that no other package depends on this is mostly a no-brainer still, but any exception on the rules opens the door for others wanting exceptions too, slowing down the release as it is.
greetings, martin.