On Di, 2007-03-06 at 12:29 +0100, Wouter Verhelst wrote: > 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. The fix for that bug is not easy to backport as it's not just one SVN revision but a few with interdependencies. At least IIRC, I looked at it some time ago. I would definitely love to see 1.2.3.1 in etch but I doubt it will be possible as the diff between 1.2.2.1 and 1.2.3.1 is rather large and not easy to review, not all changes are bugfixes but there are also other improvements in different libraries. We (the Mono team) decided that we won't upload 1.2.3.1 (or any other new upstream versions of mono and related software) to unstable unless it's guaranteed by the release team that it will go to etch... otherwise it will cause some unnecessary trobule to get smaller fixes into etch without going through unstable first... Apart from that I don't know about a single regression from 1.2.2.1 to 1.2.3.1 until now, only general improvements. Bye
Attachment:
signature.asc
Description: This is a digitally signed message part