Please add mono 1.2.3.1 to unstable (and, eventually, etch) rather than experimental

[Wouter Verhelst <wouter@debian.org>]

Hi,

I know this is going to be kinda controversial, but I'd really like to
make a case to either upload mono 1.2.3.1 to unstable (and eventually
have it migrate to etch), or to at least backport the fix for #403495 to
the version in unstable.

Justification: I filed #403495 at the severity "important", but that's
because having an application crash *sometimes* after extensive use is
something most people can live with; however, if one wants to use it in
any level of enterprise-class "production", having a runtime environment
that crashes after some serious load is totally useless (it really is
load-related, as the bug triggers when the JIT compiler misinterprets
its own cache).

I think releasing etch with this bug would be a serious showstopper for
powerpc users of mono.

-- 
<Lo-lan-do> Home is where you have to wash the dishes.
  -- #debian-devel, Freenode, 2004-09-22