case-insensitive 1.0 about stackage

[aristidb]

Should be solved with http-types 0.8.0.

2013/1/28 Michael Snoyman [email protected]

hoogle-4.2.14 (Neil Mitchell @ndmitchell https://github.com/ndmitchell)
cannot use:

• case-insensitive-1.0 -- >=0.2 && <0.5

http-types-0.7.3.0.1 ([email protected] @aristidbhttps://github.com/aristidb)
cannot use:

• case-insensitive-1.0 -- >=0.2 && <0.5

  —
  Reply to this email directly or view it on GitHubhttps://github.com//issues/39.

[snoyberg]

Great, all I have to do is update all my packages to work with http-types 0.8.0 ;).

[aristidb]

Sorry, the mass removal of deprecated functions was long overdue. :)
Am 29.01.2013 09:38 schrieb "Michael Snoyman" [email protected]:

Great, all I have to do is update all my packages to work with http-types
0.8.0 ;).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/39#issuecomment-12825048.

[ndmitchell]

hoogle-4.2.15 now allows case-insensitive-1.0 and http-types 0.8.

If Stackage is automatically compiling my code on every package bump, I wonder if I should leave my upper bounds entirely open ended, then scramble into action when something breaks (rare), rather than regularly bumping bounds?

[snoyberg]

@ndmitchell That's been a debate in the community for a while now. I think @bos kicked that off with:

http://www.haskell.org/pipermail/haskell-cafe/2012-August/102885.html

I agree with Bryan on this one, and I've started removing upper bounds. Part of the motivation behind Stackage is that it makes it (relatively) safe to remove these upper bounds since- if there is breakage- you'll find out within a day.

[aristidb]

Does Stackage run the tests, too?

Just in case there is runtime breakage on version bump...

Am Dienstag, 29. Januar 2013 schrieb Michael Snoyman :

@ndmitchell https://github.com/ndmitchell That's been a debate in the
community for a while now. I think @bos https://github.com/bos kicked
that off with:

http://www.haskell.org/pipermail/haskell-cafe/2012-August/102885.html

I agree with Bryan on this one, and I've started removing upper bounds.
Part of the motivation behind Stackage is that it makes it (relatively)
safe to remove these upper bounds since- if there is breakage- you'll
find out within a day.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/39#issuecomment-12829466.

[snoyberg]

Yes, every time our Jenkins server runs a Stackage build, it runs the tests too. If there are test failures, I'll notify you as well.