Remove mention of "experimental" releases, we have no such checks
commitd81fb0c0c66c9a9a0dde96ebaee1f738599c48ab
authorAdam Bergmark <adam@bergmark.nl>
dateSun 26 Nov 2017, 14:38 (9 years ago)
parent2ad9eac
MAINTAINERS.md+1−1
@@ -62,7 +62,7 @@ effort basis.
6262
6363## Uploading a new package version
6464
65−When a new version of a package in Stackage is uploaded to Hackage, we automatically try to include it in Stackage (unless the new version is considered experimental). That can result in a number of possible failures. If there is a failure we temporarily introduce an upper bound, and open a GitHub issue ticket to resolve the issue.
65+When a new version of a package in Stackage is uploaded to Hackage, we automatically try to include it in Stackage. That can result in a number of possible failures. If there is a failure we temporarily introduce an upper bound, and open a GitHub issue ticket to resolve the issue.
6666
6767If the new version doesn't compile then the package author should upload a fixed version.
6868