From 2ad9eac29fa19825d3882f870c0762f086d63e3b Mon Sep 17 00:00:00 2001 From: Adam Bergmark Date: Sun, 26 Nov 2017 14:33:23 +0100 Subject: [PATCH] Move github notification section below adding packages --- MAINTAINERS.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/MAINTAINERS.md b/MAINTAINERS.md index 0f6ad71b..2aab0941 100644 --- a/MAINTAINERS.md +++ b/MAINTAINERS.md @@ -8,19 +8,6 @@ The idea behind Stackage is that, if all packages work with the newest versions Packages in Stackage are not patched: all package changes occur upstream in Hackage. -## Github and Notifications - -Stackage uses Github notifications to reduce overhead of contacting individual -package maintainers through various channels. As a package maintainer, you will -receive notifications for a number of reasons, package build failures of -different sorts, blockages and bounds issues, etc. - -Please note, Github does some throttling on the number people that can be -notified within one issue. This means that on issues created with a large -number of packages affected, maintainers may not receive a notification. This -is not ideal, but Stackage is largely a manual process and done on a best -effort basis. - ## Adding a package Anyone 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 by making sure the latest version is listed at https://github.com/commercialhaskell/all-cabal-metadata/tree/master/packages/. +## Github and Notifications + +Stackage uses Github notifications to reduce overhead of contacting individual +package maintainers through various channels. As a package maintainer, you will +receive notifications for a number of reasons, package build failures of +different sorts, blockages and bounds issues, etc. + +Please note, Github does some throttling on the number people that can be +notified within one issue. This means that on issues created with a large +number of packages affected, maintainers may not receive a notification. This +is not ideal, but Stackage is largely a manual process and done on a best +effort basis. + ## Uploading a new package version 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.