Skip to content
Snippets Groups Projects
Commit 38adb9a9 authored by totten's avatar totten
Browse files

Normalize bullets

parent 90cfefa1
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/4.6-final.md
+ 16
− 16
View file @ 38adb9a9
......@@ -6,22 +6,22 @@ See [Prerequisites](any-prereq.md)
## 1: Sanity checks
* Note the original branch, such as `4.6`.
* Note the intended version, such as `4.6.28` or `4.6.29`.
* In civicrm-core.git repo, check that the code in `4.6` correctly references `4.6.X`:
* https://github.com/civicrm/civicrm-core/blob/4.6/xml/version.xml
* https://github.com/civicrm/civicrm-core/blob/4.6/sql/civicrm_generated.mysql
* https://github.com/civicrm/civicrm-core/tree/4.6/CRM/Upgrade/Incremental
* In Jenkins, review the scheduled tests for `4.6` and determine if anything should block the RC.
* https://test.civicrm.org/job/CiviCRM-Core-Matrix/
* Compare the git revisions
* https://download.civicrm.org/latest/civicrm-46NIGHTLY-drupal.tar.gz/inspect
* https://github.com/civicrm/civicrm-core/commits/4.6
* https://github.com/civicrm/civicrm-drupal/commits/6.x-4.6
* https://github.com/civicrm/civicrm-drupal/commits/7.x-4.6
* https://github.com/civicrm/civicrm-joomla/commits/4.6
* https://github.com/civicrm/civicrm-packages/commits/4.6
* https://github.com/civicrm/civicrm-wordpress/commits/4.6
* Note the original branch, such as `4.6`.
* Note the intended version, such as `4.6.28` or `4.6.29`.
* In civicrm-core.git repo, check that the code in `4.6` correctly references `4.6.X`:
* https://github.com/civicrm/civicrm-core/blob/4.6/xml/version.xml
* https://github.com/civicrm/civicrm-core/blob/4.6/sql/civicrm_generated.mysql
* https://github.com/civicrm/civicrm-core/tree/4.6/CRM/Upgrade/Incremental
* In Jenkins, review the scheduled tests for `4.6` and determine if anything should block the RC.
* https://test.civicrm.org/job/CiviCRM-Core-Matrix/
* Compare the git revisions
* https://download.civicrm.org/latest/civicrm-46NIGHTLY-drupal.tar.gz/inspect
* https://github.com/civicrm/civicrm-core/commits/4.6
* https://github.com/civicrm/civicrm-drupal/commits/6.x-4.6
* https://github.com/civicrm/civicrm-drupal/commits/7.x-4.6
* https://github.com/civicrm/civicrm-joomla/commits/4.6
* https://github.com/civicrm/civicrm-packages/commits/4.6
* https://github.com/civicrm/civicrm-wordpress/commits/4.6
## 2: Identify the final RC
......
doc/4.7-final.md
+ 19
− 19
View file @ 38adb9a9
......@@ -9,19 +9,19 @@ See [Prerequisites](any-prereq.md)
## 1: Sanity checks
* Check release notes: https://github.com/civicrm/civicrm-core/tree/4.7.X-rc/release-notes
* In Jenkins, review the scheduled tests for `4.7.X-rc` and determine if anything should block the release.
* Check release notes: https://github.com/civicrm/civicrm-core/tree/4.7.X-rc/release-notes
* In Jenkins, review the scheduled tests for `4.7.X-rc` and determine if anything should block the release.
* https://test.civicrm.org/job/CiviCRM-Core-Matrix/
* https://test.civicrm.org/job/CiviCRM-Ext-Matrix/
* Compare the git revisions
* https://download.civicrm.org/latest/civicrm-RC-drupal.tar.gz/inspect
* https://github.com/civicrm/civicrm-core/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-backdrop/commits/1.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/commits/6.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/commits/7.x-4.7.X-rc
* https://github.com/civicrm/civicrm-joomla/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-packages/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-wordpress/commits/4.7.X-rc
* Compare the git revisions
* https://download.civicrm.org/latest/civicrm-RC-drupal.tar.gz/inspect
* https://github.com/civicrm/civicrm-core/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-backdrop/commits/1.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/commits/6.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/commits/7.x-4.7.X-rc
* https://github.com/civicrm/civicrm-joomla/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-packages/commits/4.7.X-rc
* https://github.com/civicrm/civicrm-wordpress/commits/4.7.X-rc
## 2: Identify the final RC
......@@ -68,14 +68,14 @@ releaser gs://civicrm-build/4.7.19-rc/civicrm-4.7.19-201705030600.json --publish
You might want to spot-check a few URLs to ensure the tags were published, e.g.
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X
* https://github.com/civicrm/civicrm-core/tree/4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X
* https://github.com/civicrm/civicrm-joomla/tree/4.7.X
* https://github.com/civicrm/civicrm-packages/tree/4.7.X
* https://github.com/civicrm/civicrm-wordpress/tree/4.7.X
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X
* https://github.com/civicrm/civicrm-core/tree/4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X
* https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X
* https://github.com/civicrm/civicrm-joomla/tree/4.7.X
* https://github.com/civicrm/civicrm-packages/tree/4.7.X
* https://github.com/civicrm/civicrm-wordpress/tree/4.7.X
## 4: Update `versions.json`
......
doc/4.7-rc.md
+ 25
− 25
View file @ 38adb9a9
......@@ -67,42 +67,42 @@ git scan push -p origin 4.7.X-rc
You might want to spot-check a few URLs to ensure the branches were published, e.g.
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X-rc
* https://github.com/civicrm/civicrm-core/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X-rc
* https://github.com/civicrm/civicrm-joomla/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-packages/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-wordpress/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-4.7.X-rc
* https://github.com/civicrm/civicrm-core/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/6.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/7.x-4.7.X-rc
* https://github.com/civicrm/civicrm-drupal/tree/8.x-4.7.X-rc
* https://github.com/civicrm/civicrm-joomla/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-packages/tree/4.7.X-rc
* https://github.com/civicrm/civicrm-wordpress/tree/4.7.X-rc
## 3: Setup automated processes
* Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 4.7.24-rc master`)
* Go to https://test.civicrm.org/job/CiviCRM-Ext-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 4.7.24-rc master`)
* Go to https://test.civicrm.org/job/CiviCRM-Publish/configure
* In the list of `branchNames`, remove any old RC's. Add the current RC. (ex: `master 4.6 4.7.24-rc`)
* Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 4.7.24-rc master`)
* Go to https://test.civicrm.org/job/CiviCRM-Ext-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 4.7.24-rc master`)
* Go to https://test.civicrm.org/job/CiviCRM-Publish/configure
* In the list of `branchNames`, remove any old RC's. Add the current RC. (ex: `master 4.6 4.7.24-rc`)
## 4: Publish tarballs
* Go to https://test.civicrm.org/job/CiviCRM-Publish/
* Check to see if the new branch is being built automatically. If not:
* Login (if you haven't already)
* Click "Build with parameters"
* For the branch name, enter your chosen `4.7.X-rc`.
* Go to https://test.civicrm.org/job/CiviCRM-Publish/
* Check to see if the new branch is being built automatically. If not:
* Login (if you haven't already)
* Click "Build with parameters"
* For the branch name, enter your chosen `4.7.X-rc`.
## 5: Enable branch protection
To prevent someone from accidentally deleting the new RC branch, enable protection:
* https://github.com/civicrm/civicrm-core/settings/branches
* https://github.com/civicrm/civicrm-packages/settings/branches
* https://github.com/civicrm/civicrm-backdrop/settings/branches
* https://github.com/civicrm/civicrm-drupal/settings/branches
* https://github.com/civicrm/civicrm-joomla/settings/branches
* https://github.com/civicrm/civicrm-wordpress/settings/branches
* https://github.com/civicrm/civicrm-core/settings/branches
* https://github.com/civicrm/civicrm-packages/settings/branches
* https://github.com/civicrm/civicrm-backdrop/settings/branches
* https://github.com/civicrm/civicrm-drupal/settings/branches
* https://github.com/civicrm/civicrm-joomla/settings/branches
* https://github.com/civicrm/civicrm-wordpress/settings/branches
## 6: Bump version number on `master` to `4.7.Y`
......
doc/5.x-rc.md
+ 25
− 25
View file @ 38adb9a9
......@@ -73,42 +73,42 @@ git scan push -p origin 5.X
You might want to spot-check a few URLs to ensure the branches were published, e.g.
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-5.X
* https://github.com/civicrm/civicrm-core/tree/5.X
* https://github.com/civicrm/civicrm-drupal/tree/6.x-5.X
* https://github.com/civicrm/civicrm-drupal/tree/7.x-5.X
* https://github.com/civicrm/civicrm-drupal/tree/8.x-5.X
* https://github.com/civicrm/civicrm-joomla/tree/5.X
* https://github.com/civicrm/civicrm-packages/tree/5.X
* https://github.com/civicrm/civicrm-wordpress/tree/5.X
* https://github.com/civicrm/civicrm-backdrop/tree/1.x-5.X
* https://github.com/civicrm/civicrm-core/tree/5.X
* https://github.com/civicrm/civicrm-drupal/tree/6.x-5.X
* https://github.com/civicrm/civicrm-drupal/tree/7.x-5.X
* https://github.com/civicrm/civicrm-drupal/tree/8.x-5.X
* https://github.com/civicrm/civicrm-joomla/tree/5.X
* https://github.com/civicrm/civicrm-packages/tree/5.X
* https://github.com/civicrm/civicrm-wordpress/tree/5.X
## 4: Setup automated processes
* Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 5.X master`)
* Go to https://test.civicrm.org/job/CiviCRM-Ext-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 5.X master`)
* Go to https://test.civicrm.org/job/CiviCRM-Publish/configure
* In the list of `branchNames`, remove any old RC's. Add the current RC. (ex: `master 4.6 5.X`)
* Go to https://test.civicrm.org/job/CiviCRM-Core-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 5.X master`)
* Go to https://test.civicrm.org/job/CiviCRM-Ext-Matrix/configure
* In the list of `CIVIVER`s, remove any old RC's. Add the current RC. (ex: `4.6 5.X master`)
* Go to https://test.civicrm.org/job/CiviCRM-Publish/configure
* In the list of `branchNames`, remove any old RC's. Add the current RC. (ex: `master 4.6 5.X`)
## 5: Publish tarballs
* Go to https://test.civicrm.org/job/CiviCRM-Publish/
* Check to see if the new branch is being built automatically. If not:
* Login (if you haven't already)
* Click "Build with parameters"
* For the branch name, enter your chosen `5.X`.
* Go to https://test.civicrm.org/job/CiviCRM-Publish/
* Check to see if the new branch is being built automatically. If not:
* Login (if you haven't already)
* Click "Build with parameters"
* For the branch name, enter your chosen `5.X`.
## 6: Enable branch protection
To prevent someone from accidentally deleting the new RC branch, enable protection:
* https://github.com/civicrm/civicrm-core/settings/branches
* https://github.com/civicrm/civicrm-packages/settings/branches
* https://github.com/civicrm/civicrm-backdrop/settings/branches
* https://github.com/civicrm/civicrm-drupal/settings/branches
* https://github.com/civicrm/civicrm-joomla/settings/branches
* https://github.com/civicrm/civicrm-wordpress/settings/branches
* https://github.com/civicrm/civicrm-core/settings/branches
* https://github.com/civicrm/civicrm-packages/settings/branches
* https://github.com/civicrm/civicrm-backdrop/settings/branches
* https://github.com/civicrm/civicrm-drupal/settings/branches
* https://github.com/civicrm/civicrm-joomla/settings/branches
* https://github.com/civicrm/civicrm-wordpress/settings/branches
## 7: Bump version number on `master` to `5.Y.alpha1`
......
doc/any-announce.md
+ 6
− 6
View file @ 38adb9a9
......@@ -33,11 +33,11 @@ Example announcement template:
## Blog
[Post to the blog](http://civicrm.org/blog). A few things to ensure:
* The author of the blog should be Drupal user `dev-team`. (If you don't have rights to specify the blog's author, and if you don't have a password for `dev-team`, then PM `totten` for the credentials.)
* Check "Promote to Front Page" so blog appears on home page banner (below gallery).
* Blog should include release highlights.
* List of CONTRIBUTORS should be reviewed and updated (process TBD). (*Is this still relevant now that we have better relase notes?*)
* The author of the blog should be Drupal user `dev-team`. (If you don't have rights to specify the blog's author, and if you don't have a password for `dev-team`, then PM `totten` for the credentials.)
* Check "Promote to Front Page" so blog appears on home page banner (below gallery).
* Blog should include release highlights.
* List of CONTRIBUTORS should be reviewed and updated (process TBD). (*Is this still relevant now that we have better relase notes?*)
## Twitter
......@@ -47,5 +47,5 @@ Post to Twitter as "@civicrm" (or ping the `marketing` channel on Mattermost). I
Update Versions in JIRA (http://issues.civicrm.org/jira/plugins/servlet/project-config/CRM/versions) (TODO: does JIRA have an api we could tap into to add this step to the releaser script?)
* Mark this version as released
* Add 'next' versions (should be two future versions present on active branch - e.g. when 4.7.1 is released, should be 4.7.2 and 4.7.3)
* Mark this version as released
* Add 'next' versions (should be two future versions present on active branch - e.g. when 4.7.1 is released, should be 4.7.2 and 4.7.3)
doc/any-major.md
+ 10
− 10
View file @ 38adb9a9
If this is a major release (e.g. 4.7.0):
* check that wiki doc header and versions widget are updated.
* Check Downloads page and links in CiviCRM.org. (this appears to be invalid?)
* Check https://civicrm.org/download/list
* ~~update download links which appear on CiviCRM.org home page Download tab~~
* ~~search for content of type Download and update the links for each release with corresponding download link~~
* (I don't see these links, and the content in the nodes looks ancient – 4.4)
* Update the links in the demo and sandbox pages so that they reflect the latest version: https://civicrm.org/go/demo and http://civicrm.org/sandboxes
* Update the Jenkins jobs https://test.civicrm.org/view/Sites/job/demo.civicrm.org/
* Check latest.civicrm.org/versions.json to make sure this version has changed from "testing" to "stable" and previous stable version is either "lts" or "eol"
* Increment this section title (wink)
* check that wiki doc header and versions widget are updated.
* Check Downloads page and links in CiviCRM.org. (this appears to be invalid?)
* Check https://civicrm.org/download/list
* ~~update download links which appear on CiviCRM.org home page Download tab~~
* ~~search for content of type Download and update the links for each release with corresponding download link~~
* (I don't see these links, and the content in the nodes looks ancient – 4.4)
* Update the links in the demo and sandbox pages so that they reflect the latest version: https://civicrm.org/go/demo and http://civicrm.org/sandboxes
* Update the Jenkins jobs https://test.civicrm.org/view/Sites/job/demo.civicrm.org/
* Check latest.civicrm.org/versions.json to make sure this version has changed from "testing" to "stable" and previous stable version is either "lts" or "eol"
* Increment this section title (wink)
doc/any-prereq.md
+ 8
− 8
View file @ 38adb9a9
......@@ -2,14 +2,14 @@
## Pre-requisites
* Installed+configured [Google Cloud SDK](https://cloud.google.com/sdk/downloads). (Run `gcloud init`, `gcloud auth activate-service-account --key-file ...`, or similar.)
* Write access to all main CiviCRM GitHub repos (`civicrm-{core,packages,backdrop,drupal,joomla,wordpress}`)
* Write access to Google Cloud Storage (`civicrm` and `civicrm-build` buckets)
* Write access to SourceForge account (`civicrm`)
* Access to CiviCRM Jenkins (https://test.civicrm.org)
* Import the CiviCRM GPG keypair (`7A1E75CB`)
* Local copy of [buildkit](https://github.com/civicrm/civicrm-buildkit/)
* Local clones of all main CiviCRM git repos (e.g. `mkdir src; cd src; gitify all --skip-gencode` or `cividist create dist`)
* Installed+configured [Google Cloud SDK](https://cloud.google.com/sdk/downloads). (Run `gcloud init`, `gcloud auth activate-service-account --key-file ...`, or similar.)
* Write access to all main CiviCRM GitHub repos (`civicrm-{core,packages,backdrop,drupal,joomla,wordpress}`)
* Write access to Google Cloud Storage (`civicrm` and `civicrm-build` buckets)
* Write access to SourceForge account (`civicrm`)
* Access to CiviCRM Jenkins (https://test.civicrm.org)
* Import the CiviCRM GPG keypair (`7A1E75CB`)
* Local copy of [buildkit](https://github.com/civicrm/civicrm-buildkit/)
* Local clones of all main CiviCRM git repos (e.g. `mkdir src; cd src; gitify all --skip-gencode` or `cividist create dist`)
The user `releaser` on `latest.civicrm.org` has a suitable configuration in `~/src/4.6`, `~/src/4.7`, and `~/src/master`.
To start a session, login to that account and run:
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment