git.iko.soy/stackage
on master help sign in
Merge pull request #5390 from galenhuntington/master
e4491ddJoe Kachmar
DATA-FLOW.md+1−1
compare with master
unifiedsplit
@@ -26,7 +26,7 @@ There are three inputs into the data flow:
26## Travis
26## Travis
27
27
28For [various
28For [various
29−reasons](https://www.fpcomplete.com/blog/2015/05/distributing-packages-without-sysadmin),
29+reasons](https://tech.fpcomplete.com/blog/2015/05/distributing-packages-without-sysadmin),
30we leverage Travis CI for running some processes. In particular:
30we leverage Travis CI for running some processes. In particular:
31
31
32* [all-cabal-files](https://github.com/commercialhaskell/all-cabal-files/blob/hackage/.travis.yml)
32* [all-cabal-files](https://github.com/commercialhaskell/all-cabal-files/blob/hackage/.travis.yml)
MAINTAINERS.md+1−1
@@ -4,7 +4,7 @@ The idea behind Stackage is that, if all packages work with the newest versions
4
4
5* All packages are buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
5* All packages are buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
6* All packages are compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
6* All packages are compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
7−* All packages in a snapshot are compatible with the versions of libraries that ship with the GHC used in the snapshot ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
7+* All packages in a snapshot are compatible with the versions of libraries that ship with the GHC used in the snapshot ([more information on lenient lower bounds](https://tech.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
8
8
9Packages in Stackage are not patched: all package changes occur upstream in Hackage.
9Packages in Stackage are not patched: all package changes occur upstream in Hackage.
10
10
README.md+3−3
@@ -20,7 +20,7 @@ We welcome all packages, provided:
20* The package author/maintainer agrees to the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md).
20* The package author/maintainer agrees to the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md).
21* The package is buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
21* The package is buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
22* The package is compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
22* The package is compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
23−* The package is compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
23+* The package is compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://tech.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
24
24
25Full details on how to add and test a package can be found in the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#adding-a-package).
25Full details on how to add and test a package can be found in the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#adding-a-package).
26
26
@@ -109,14 +109,14 @@ There are a number of answers to this question:
109 and packages depending on them - are fixed to GHC versions. Common
109 and packages depending on them - are fixed to GHC versions. Common
110 examples of this are containers and transformers. There's a lot more
110 examples of this are containers and transformers. There's a lot more
111 information on this in
111 information on this in
112− [an FP Complete blog post](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)
112+ [an FP Complete blog post](https://tech.fpcomplete.com/blog/2014/05/lenient-lower-bounds)
113
113
114__How long do you maintain an LTS build?__
114__How long do you maintain an LTS build?__
115
115
116We only guarantee that we will maintain a single LTS major version at
116We only guarantee that we will maintain a single LTS major version at
117a time, and that it will be maintained for at least three months. This
117a time, and that it will be maintained for at least three months. This
118is the
118is the
119−[originally proposed support window](https://www.fpcomplete.com/blog/2014/12/backporting-bug-fixes),
119+[originally proposed support window](https://tech.fpcomplete.com/blog/2014/12/backporting-bug-fixes),
120and hasn't changed since then.
120and hasn't changed since then.
121
121
122That said, we do maintain the capability to keep multiple LTS runs
122That said, we do maintain the capability to keep multiple LTS runs