Hello, On Mon, May 23, 2016 at 10:05:21AM +0200, Joachim Breitner wrote: > 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. Can package-plan.pl keep track of what stage we're at? Can you tell it "right now we're doing stackage nightly/LTS 6" and it'll tell us what to upgrade based on that? > 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! Thanks for the encouragement. Let me take this opportunity to ask a few general questions. 1. Are there enough DDs watching commits to DHG_packages such that running `dch -r` is sufficient to request sponsorship, or should we drop a note somewhere? 2. Right now, most of the packages on my DDPO are end-user programs rather than libraries. So before I request sponsorship for new upstream versions, after the usual automated tests, I also install and try to *use* the new version. This doesn't really apply to new versions of libraries. Is it okay to go ahead and request sponsorship after running package-plan.pl, sbuild, lintian, piuparts and adt-run, and fixing any problems those tools come up with? It makes me a little queasy not to actually use the package, but I guess that team-maintained libraries are quite different from end-user programs. On Mon, May 23, 2016 at 09:04:13PM +0200, Iustin Pop wrote: > Quick question: does this mean that we'll skip LTS 5? I.e., should > packages be kept at LTS 4 until we move to LTS 6? I think Joachim is suggesting that until LTS 5 is released, we're tracking Stackage nightly. I think the point is that we want LTS 7 in stretch, but our fallback is LTS 6 in stretch if we don't manage that; until we reach LTS 6, no need for a freeze on an LTS version. -- Sean Whitton
Attachment:
signature.asc
Description: PGP signature