git.iko.soy/stackage
on master help sign in
Merge pull request #5390 from galenhuntington/master

Fix blog links.

commite4491dd495b5cab6288e41e0301e57477f4f9dd9 authorJoe Kachmar <joseph.kachmar@gmail.com> dateMon 25 May 2020, 13:27 (6 years ago) parentd83561a8673eae
3 files changed+5−5
compare with master
unifiedsplit
DATA-FLOW.md+1−1 MAINTAINERS.md+1−1 README.md+3−3
DATA-FLOW.md+1−1
@@ -26,7 +26,7 @@ There are three inputs into the data flow:
2626## Travis
2727
2828For [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),
3030we leverage Travis CI for running some processes. In particular:
3131
3232* [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
44
55* 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.
66* 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)).
88
99Packages in Stackage are not patched: all package changes occur upstream in Hackage.
1010
README.md+3−3
@@ -20,7 +20,7 @@ We welcome all packages, provided:
2020* The package author/maintainer agrees to the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md).
2121* 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.
2222* 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)).
2424
2525Full 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).
2626
@@ -109,14 +109,14 @@ There are a number of answers to this question:
109109 and packages depending on them - are fixed to GHC versions. Common
110110 examples of this are containers and transformers. There's a lot more
111111 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)
113113
114114__How long do you maintain an LTS build?__
115115
116116We only guarantee that we will maintain a single LTS major version at
117117a time, and that it will be maintained for at least three months. This
118118is 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),
120120and hasn't changed since then.
121121
122122That said, we do maintain the capability to keep multiple LTS runs