From 1693e7a9c665b7dc703f82a2f2199033409c3a2b Mon Sep 17 00:00:00 2001
From: Tim Otten <totten@civicrm.org>
Date: Mon, 15 May 2017 14:52:12 -0500
Subject: [PATCH] Update 4.6-final.md - Fix new references to branch names
---
doc/4.6-final.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/4.6-final.md b/doc/4.6-final.md
index f6c47d9..1064f1a 100644
--- a/doc/4.6-final.md
+++ b/doc/4.6-final.md
@@ -16,10 +16,10 @@ The user `releaser` on `latest.civicrm.org` has a suitable configuration in `~/s
* 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 `master` correctly references `4.6.X`:
- * https://github.com/civicrm/civicrm-core/blob/master/xml/version.xml
- * https://github.com/civicrm/civicrm-core/blob/master/sql/civicrm_generated.mysql
- * https://github.com/civicrm/civicrm-core/tree/master/CRM/Upgrade/Incremental
+ * 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/
--
GitLab