Updating list of assignments in release templates. Removing old procedures that were moved to wiki.

Author: quicksketch

README.md

@@ -1,5 +1,3 @@
-[![Open Source Helpers](https://www.codetriage.com/backdrop/backdrop-issues/badges/users.svg)](https://www.codetriage.com/backdrop/backdrop-issues)
-
 Backdrop Issue Tracker
 ======================
 
@@ -55,5 +53,6 @@ experience by providing answers of your own. Come join the community!
 Procedures
 ----------
 
-We have a library of internal procedures stored in a [sub-directory within this
-repository](https://github.com/backdrop/backdrop-issues/tree/master/procedures).
+We have a library of internal procedures stored in a [this repository's wiki](https://github.com/backdrop/backdrop-issues/wiki/).
+
+And a set of templates for creating issues is within the [templates directory](https://github.com/backdrop/backdrop-issues/tree/main/procedures).

procedures/core--commit-procedure.md

@@ -6,20 +6,20 @@ Steps to create a SECURITY (BUG-FIX) release
 Issue Title:   Backdrop 1.x.x Release checklist
 ---
 
-Release scheduled for MM DD, 20xx 10am - 4pm PT
+Release scheduled for [Month] DD, 20xx 10am - 4pm PT
 
 ## Pre-release tasks
 
-- [ ] Merge commits (assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Merge commits (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create the next bugfix milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Move all unfinished issues to the next bugfix release milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Review all closed issues in milestone: (assign to klonos / jenlampton / stpaultim )
   * Issue titles should include a complete, but very brief summary of the problem.
-  * Issue titles sould be in complete sentences, ending with a period.
+  * Issue titles should be in complete sentences, ending with a period.
   * Bug issue titles should start with `Fix` or `Fixed`,
-  * New fearure issue titles should start with `Add` or `Added`.
+  * New feature issue titles should start with `Add` or `Added`.
   * Each issue should have accurate labels, especially the "type - " labels.
-- [ ] Close the milestone (assign to quicksketch  herbdool / bwpanda)
+- [ ] Close the milestone (assign to quicksketch / herbdool)
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * "Security release for Backdrop CMS. This release fixes 1 security vulnerability:"
@@ -37,14 +37,16 @@ Release scheduled for MM DD, 20xx 10am - 4pm PT
     * Select the most recent time "Release Notes Generator" has been run.
     * Download the `release-notes` artifact attached to the generator.
     * Unzip the file, and copy/pate contents into release notes draft.
-    * Remove any square bracets in the titles, and move those issues to their own section.
+    * Remove any square brackets in the titles, and move those issues to their own section.
 - [ ] Draft Security Advisories (assign to stpaultim / klonos / jenlampton  herbdool / quicksketch)
 
 ## Release tasks
 
-- [ ] Update bootstrap.inc with version number (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Revert version number back (assign to quicksketch / serundeputy / herbdool / bwpanda)
+Assigned to quicksketch / herbdool / laryn / hosef
+
+- [ ] Update bootstrap.inc with version number (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Revert version number back (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create release notes on GitHub, and publish release (assign to jenlampton / herbdool / quicksketch)
 - [ ] Publish Security Advisories on b.org (assign to stpaultim / klonos / jenlampton / herbdool / quicksketch)
 - [ ] Mark the release node on b.org as a security release (assign to stpaultim / klonos / jenlampton / herbdool / quicksketch)
@@ -55,7 +57,7 @@ Release scheduled for MM DD, 20xx 10am - 4pm PT
 
 ## Immediate Post-release tasks
 
-- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @bwpanda | @klonos
+- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @klonos
 - [ ] Update [Pantheon](https://github.com/backdrop/backdrop-issues/wiki/Update:-Pantheon-Upstream) @herbdool
 - [ ] Update [Platform.sh](https://github.com/backdrop/backdrop-issues/wiki/Update:-Platform.sh-Template) (assign to herbdool / jenlampton)
 - [ ] Update [Composer](https://github.com/backdrop-ops/backdrop-composer) @herbdool (or quicksketch)
@@ -68,13 +70,12 @@ Release scheduled for MM DD, 20xx 10am - 4pm PT
 
 ## Backdrop's Website updates
 
-- [ ] backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] beta.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] docs.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] events.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] forum.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] localize.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-
+- [ ] backdropcms.org @jenlampton (or bugfolder)
+- [ ] beta.backdropcms.org @jenlampton (or bugfolder)
+- [ ] docs.backdropcms.org @jenlampton (or bugfolder)
+- [ ] events.backdropcms.org @jenlampton (or bugfolder)
+- [ ] forum.backdropcms.org @jenlampton (or bugfolder)
+- [ ] localize.backdropcms.org @jenlampton (or bugfolder)
 
 ## See Also
 

procedures/core--release-notes.md

@@ -6,20 +6,20 @@ Steps to create a BUG-FIX release
 Issue Title:   Backdrop 1.x.x Release checklist
 ---
 
-Release scheduled for MM DD, 20xx 10am - 4pm PT
+Release scheduled for [Month] DD, 20xx 10am - 4pm PT
 
 ## Pre-release tasks
 
-- [ ] Merge commits (assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Merge commits (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create the next bugfix milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Move all unfinished issues to the next bugfix release milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Review all closed issues in milestone: (assign to klonos / jenlampton / stpaultim )
   * Issue titles should include a complete, but very brief summary of the problem.
-  * Issue titles sould be in complete sentences, ending with a period.
+  * Issue titles should be in complete sentences, ending with a period.
   * Bug issue titles should start with `Fix` or `Fixed`,
-  * New fearure issue titles should start with `Add` or `Added`.
+  * New feature issue titles should start with `Add` or `Added`.
   * Each issue should have accurate labels, especially the "type - " labels.
-- [ ] Close the milestone (assign to quicksketch / herbdool / bwpanda)
+- [ ] Close the milestone (assign to quicksketch / herbdool)
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * "Maintenance release for Backdrop CMS. This update contains bug fixes and usability improvements only."
@@ -36,13 +36,13 @@ Release scheduled for MM DD, 20xx 10am - 4pm PT
     * Select the most recent time "Release Notes Generator" has been run.
     * Download the `release-notes` artifact attached to the generator.
     * Unzip the file, and copy/pate contents into release notes draft.
-    * Remove any square bracets in the titles, and move those issues to their own section.
+    * Remove any square brackets in the titles, and move those issues to their own section.
 
 ## Release tasks
 
-- [ ] Update bootstrap.inc with version number (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / herbdool / bwpanda)
-- [ ] Revert version number back (assign to quicksketch / herbdool / bwpanda)
+- [ ] Update bootstrap.inc with version number (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Revert version number back (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create release notes on GitHub, and publish release (assign to jenlampton / herbdool / quicksketch)
 - [ ] Update the front page download link on b.org (assign to stpaultim / klonos / jenlampton / herbdool / quicksketch)
 - [ ] Tweet that a new release is out (assign to stpaultim / jimbirch / jenlampton / quicksketch)
@@ -51,9 +51,9 @@ Release scheduled for MM DD, 20xx 10am - 4pm PT
 ## Immediate Post-release tasks
 
 If this release does NOT accompany a minor release:
-- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @bwpanda | @klonos
+- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @klonos
 - [ ] Update [Pantheon](https://github.com/backdrop/backdrop-issues/wiki/Update:-Pantheon-Upstream) @herbdool
-- [ ] Update [Platform.sh](https://github.com/backdrop/backdrop-issues/wiki/Update:-Platform.sh-Template) (assign to herbdool, jenlampton)
+- [ ] Update [Platform.sh](https://github.com/backdrop/backdrop-issues/wiki/Update:-Platform.sh-Template) (assign to herbdool / jenlampton)
 - [ ] Update [Composer](https://github.com/backdrop-ops/backdrop-composer) @herbdool (or quicksketch)
 - [ ] Update [Docker](https://github.com/backdrop/backdrop-issues/wiki/Update:-Docker-Image) @wylbur
 - [ ] Update the Wikipedia articles (assign to stpaultim / klonos)
@@ -65,13 +65,12 @@ If this release does NOT accompany a minor release:
 ## Backdrop's Website updates
 <!-- If this release does NOT accompany a minor release: -->
 
-- [ ] backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] beta.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] docs.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] events.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] forum.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-- [ ] localize.backdropcms.org @jenlampton (or bwpanda / bugfolder)
-
+- [ ] backdropcms.org @jenlampton (or bugfolder)
+- [ ] beta.backdropcms.org @jenlampton (or bugfolder)
+- [ ] docs.backdropcms.org @jenlampton (or bugfolder)
+- [ ] events.backdropcms.org @jenlampton (or bugfolder)
+- [ ] forum.backdropcms.org @jenlampton (or bugfolder)
+- [ ] localize.backdropcms.org @jenlampton (or bugfolder)
 
 ## See Also
 

procedures/event--backdrop-live.md

@@ -1,20 +1,20 @@
 Steps to create a MAJOR release
 =================================
-
+(assignments below are in order of preference from left to right)
 
 ## Pre-release tasks
 
-- [ ] Merge commits (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Create a new minor release ((assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Merge commits (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Create a new minor release ((assign to quicksketch / serundeputy / herbdool)
 - [ ] Create the next minor milestone (assign to quicksketch / jenlampton)
 - [ ] Move all unfinished issues to the next major release milestone (assign to quicksketch / jenlampton)
 - [ ] Review all closed issues in milestone: (assign to klonos / jenlampton / stpaultim )
   * Issue titles should include a complete, but very brief summary of the problem.
-  * Issue titles sould be in complete sentences, ending with a period.
+  * Issue titles should be in complete sentences, ending with a period.
   * Bug issue titles should start with `Fix` or `Fixed`,
-  * New fearure issue titles should start with `Add` or `Added`.
+  * New feature issue titles should start with `Add` or `Added`.
   * Each issue should have accurate labels, especially the "type - " labels.
-- [ ] Close the milestone (assign to quicksketch / herbdool / bwpanda)
+- [ ] Close the milestone (assign to quicksketch / herbdool)
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
     * This is the preview release of Backdrop 1.16.0. Please use this version if you would like to help us test the features in the new version of Backdrop prior to the official release on January/May/September 15th, 20xx.
@@ -35,21 +35,19 @@ Steps to create a MAJOR release
 - [ ] Draft blog post (assign to tomgrandy / klonos / jenlampton / quicksketch)
 - [ ] Draft a newsletter via MailChimp (assign to facetinteractive / tomgrandy / jenlampton)
 
-
 ## Release tasks
 
-- [ ] Update bootstrap.inc with version number (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Revert version number back (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Create release notes on GitHub (assign to serundeputy / quicksketch / jenlampton)
-- [ ] Unpublish preview release on backdropcms.org (assign to serundeputy / quicksketch / jenlampton)
+- [ ] Update bootstrap.inc with version number (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Revert version number back (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Create release notes on GitHub (assign to quicksketch / jenlampton)
+- [ ] Unpublish preview release on backdropcms.org (assign to quicksketch / jenlampton)
 - [ ] Update the front page download link on b.org (assign to serundeputy / quicksketch / jenlampton / klonos)
 - [ ] Tweet that a new release is out (assign to quicksketch / jenlampton / jimbirch)
 
-
 ## Post-release tasks (after first bug-fix release or 14 days -- whichever comes sooner)
 
-- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @bwpanda | @klonos
+- [ ] Update [Tugboat](https://github.com/backdrop/backdrop-issues/wiki/Update:-Tugboat) @klonos
 - [ ] Update [Pantheon](https://github.com/backdrop/backdrop-issues/wiki/Update:-Pantheon-Upstream) @herbdool
 - [ ] Update [Platform.sh](https://github.com/backdrop/backdrop-issues/wiki/Update:-Platform.sh-Template) (assign to herbdool / jenlampton)
 - [ ] Update [Composer](https://github.com/backdrop-ops/backdrop-composer) @herbdool (or quicksketch)
@@ -66,6 +64,9 @@ Steps to create a MAJOR release
       * https://en.wikipedia.org/wiki/Backdrop_CMS
       * https://en.wikipedia.org/wiki/List_of_content_management_systems
 
+## See Also
 
-See the Accompanying Bug-Fix Release Checklist
-----------------------------------------------
+<!-- If this release DOES accompany a minor release: -->
+- [Minor Release Checklist]()
+<!-- If this is a security release: -->
+- [Checklist for previous minor version]()

procedures/leadership--add-core-committer.md

@@ -1,6 +1,5 @@
 DRAFT Steps to create a MINOR PREVIEW release
 =====================================
-
 (assignments below are in order of preference from left to right)
 
 ---
@@ -12,14 +11,14 @@ Scheduled for January/May/September 1st, 20xx 10am - 4pm PT
 ## Pre-release tasks
 
 - [ ] If this is the Jan 1 pre-release, then make sure to update the end year in the "All Backdrop code is Copyright..." section towards the bottom of the README.md file.
-- [ ] Merge commits (assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Merge commits (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create a new minor release milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Move all unfinished issues to the next minor release milestone (assign to klonos / jenlampton / herbdool / quicksketch)
 - [ ] Review all closed issues in milestone: (assign to klonos / jenlampton / stpaultim )
   * Issue titles should include a complete, but very brief summary of the problem.
-  * Issue titles sould be in complete sentences, ending with a period.
+  * Issue titles should be in complete sentences, ending with a period.
   * Bug issue titles should start with `Fix` or `Fixed`,
-  * New fearure issue titles should start with `Add` or `Added`.
+  * New feature issue titles should start with `Add` or `Added`.
   * Each issue should have accurate labels, especially the "type - " labels.
 - [ ] Draft Release notes (assign to jenlampton / herbdool / quicksketch)
   - [ ] Include a short, descriptive summary of the release, for example:
@@ -39,7 +38,6 @@ Scheduled for January/May/September 1st, 20xx 10am - 4pm PT
       * Unzip the file, and copy/pate contents into release notes draft.
       * Re-word issue titles to indicate that the problems have been fixed.
 
-
 ## Pre-release Publicity + documentation tasks
 
 - [ ] Review issues for new features (assign to @jenlampton / @klonos / @cellear)
@@ -53,26 +51,27 @@ Scheduled for January/May/September 1st, 20xx 10am - 4pm PT
 - [ ] Update list of modules included in backdrop_upgrade_status module (assign to jenlampton)
 - [ ] Create new forum topic for feedback on the release @stpaultim
 
-
 ## Release tasks
 
-- [ ] Update bootstrap.inc with version number (e.g. `1.10.0-preview`) (assign to quicksketch / serundeputy / herbdool / bwpanda)
-- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Update bootstrap.inc with version number (e.g. `1.10.0-preview`) (assign to quicksketch / herbdool / laryn / hosef)
+- [ ] Tag for release, and push tag to GitHub (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Note: New incremented branch for development is usually created on release day
-- [ ] Revert version number back on 1.x branch with the same minor number (e.g. `1.10.x-dev`) (assign to quicksketch / serundeputy / herbdool / bwpanda)
+- [ ] Revert version number back on 1.x branch with the same minor number (e.g. `1.10.x-dev`) (assign to quicksketch / herbdool / laryn / hosef)
 - [ ] Create release notes on GitHub **Important: Check "This is a pre-release" checkbox when creating release** (assign to jenlampton / herbdool / quicksketch)
 
-
 ## Website updates
-- [ ] beta.backdropcms.org (assign to @jenlampton / @bwpanda / @bugfolder)
 
+- [ ] beta.backdropcms.org @jenlampton (or bugfolder)
+- [ ] docs.backdropcms.org @jenlampton (or bugfolder)
+- [ ] events.backdropcms.org @jenlampton (or bugfolder)
+- [ ] forum.backdropcms.org @jenlampton (or bugfolder)
+- [ ] localize.backdropcms.org @jenlampton (or bugfolder)
 
 ## Post-release Publicity + documentation tasks
 
 - [ ] Tweet that a preview release is out (assign to stpaultim / jimbirch / jenlampton / quicksketch)
 - [ ] Publish roadmap updates for backdropcms.org (assign to stpaultim / klonos / jenlampton)
 
-
 See Also
 ---------
 * [Bug-Fix Release Checklist]()