Hi, this blog post is relevant for us: https://unknownparallel.wordpress.com/2016/05/22/stackage-lts-and-ghc-8 -0/ This suits us quite well. Here is what I propose: * We busily update packages to Stackage nightly, and upload to unstable. * When LTS 6 is released, we upgrade packages to that, and then freeze Haskell, so that is stabilizes and migrates to testing. * Mumble mumble (see below) * When LTS 7 is released, we upload GHC 8 to unstable, upgrade packages to LTS 7, and work hard to get it into testing before the Debian freeze. The mumble mumble phase allows for two options (we don’t have to decide on that until then): A: We track Stackge Nightly and GHC-8 only in our git repository, using "dht make-all" etc. to figure out what is amiss. We do not upload to unstable until LTS 7 is released and everything works when we build it; then we upload everything in one go. This minimizes breakage in unstable, and in the mean- time we can still fix issues in testing via uploads to unstable B: We track Stackage Nightly and GHC-8 in unstable. This way, we know about arch-specific problems earlier, but unstable is broken (for a long time, I fear) and we cannot upload fixes meant for testing. We have a few new members (Sean Whitton, I’m looking at you) and a few memembers with new upload rights (Sven Bartscher, I’m looking at you). Your chance now to make a big impact! Question: How close are we to getting the current set of packages into testing? Should we wait for that (possibly staging the next set of uploads in our git repository?) Greetings, Joachim PS: PPAs would help... -- Joachim “nomeata” Breitner Debian Developer nomeata@debian.org • https://people.debian.org/~nomeata XMPP: nomeata@joachim-breitner.de • GPG-Key: 0xF0FBF51F https://www.joachim-breitner.de/
Attachment:
signature.asc
Description: This is a digitally signed message part