@@ -8,19 +8,6 @@ The idea behind Stackage is that, if all packages work with the newest versions
88
99Packages in Stackage are not patched: all package changes occur upstream in Hackage.
1010
11−## Github and Notifications
12−
13−Stackage uses Github notifications to reduce overhead of contacting individual
14−package maintainers through various channels. As a package maintainer, you will
15−receive notifications for a number of reasons, package build failures of
16−different sorts, blockages and bounds issues, etc.
17−
18−Please note, Github does some throttling on the number people that can be
19−notified within one issue. This means that on issues created with a large
20−number of packages affected, maintainers may not receive a notification. This
21−is not ideal, but Stackage is largely a manual process and done on a best
22−effort basis.
23−
2411## Adding a package
2512
2613Anyone can add any package to Stackage but you may only add packages under your own name. It's highly encouraged that the actual package maintainer is also the Stackage maintainer, if that is not the case you should drop the package maintainer a note first.
@@ -60,6 +47,19 @@ recommend waiting an hour before opening the PR. You can verify this
6047by making sure the latest version is listed at
6148https://github.com/commercialhaskell/all-cabal-metadata/tree/master/packages/.
6249
50+## Github and Notifications
51+
52+Stackage uses Github notifications to reduce overhead of contacting individual
53+package maintainers through various channels. As a package maintainer, you will
54+receive notifications for a number of reasons, package build failures of
55+different sorts, blockages and bounds issues, etc.
56+
57+Please note, Github does some throttling on the number people that can be
58+notified within one issue. This means that on issues created with a large
59+number of packages affected, maintainers may not receive a notification. This
60+is not ideal, but Stackage is largely a manual process and done on a best
61+effort basis.
62+
6363## Uploading a new package version
6464
6565When 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.