Hi, Am Freitag, den 11.09.2009, 07:02 +1000 schrieb Erik de Castro Lopo: > > This is good news. But I don't think it really changes much in the > > short term. 1.20 will not be backwards compatible with 1.13, and > > almost everyone uses the 1.13 interface right now. So, we need to keep > > both until everyone migrates. > > > > I guess it means we should plan to have both available, instead of > > just 1.13? > > This would suggest that we need a HaXmL1.13 and leave the current > HaxMl unchanged. I’m reluctant to agree here. Having two separate branches of the same software in Debian should be the exception. If HaXml-1.19 is going to be the next stable, I’d rather see the HaXml using packages follow suite and start to be compatible with that version, preferably before ghc6-6.12 is ready for the migration to squeeze. Is anyone aware of how large the API changes are? Does it require major re-writes in the using code, or just minor adjustments? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil