[thrift] branch master updated: Updated website update info, the ASF CMS is not longer used anymore.

[je...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jensg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/thrift.git


The following commit(s) were added to refs/heads/master by this push:
     new f0563a5  Updated website update info, the ASF CMS is not longer used anymore.
f0563a5 is described below

commit f0563a5c4929d169090ca8180e06895339c136bb
Author: Jens Geyer <je...@apache.org>
AuthorDate: Wed Feb 16 08:50:47 2022 +0100

    Updated website update info, the ASF CMS is not longer used anymore.
---
 doc/ReleaseManagement.md | 17 +----------------
 1 file changed, 1 insertion(+), 16 deletions(-)

diff --git a/doc/ReleaseManagement.md b/doc/ReleaseManagement.md
index 70df31c..a0c55ef 100644
--- a/doc/ReleaseManagement.md
+++ b/doc/ReleaseManagement.md
@@ -345,22 +345,7 @@ Voting on the development mailing list provides additional benefits (wisdom from
 
     The merge of 1.0.0 into master should proceed as a fast-forward since the 1.0.0 release branch.  If there are discrepancies the best thing to do is resolve them and then submit a pull request.  This pull request must be *MERGED* and not *REBASED* after the CI build is successful.  You may want to do this yourself and mark the pull request as `[DO NOT MERGE]`.
 
-1. Update the ASF CMS content for thrift to include the new release.  Note over time we will retire this in favor of including all documentation in the GitHub repository.  The page with the variables that are important like the current release or distribution links is in trunk/lib/path.pm in the ASF CMS for thrift.
-
-    1. Go to the [ASF CMS for Thrift](https://cms.apache.org/thrift/).
-    1. Get a working copy.
-    1. On the top right, click on `trunk`.
-    1. Navigate into `lib`.
-    1. Open `path.pm`.
-    1. Edit
-    1. Change `current_release` and `current_release_date` to reflect the correct information.
-    1. Submit
-    1. Commit
-    1. Submit
-    1. Follow Staging Build until it completes.
-    1. Open the Staged site.
-    1. Ensure the download links work.
-    1. Publish Site.
+1. Update the web site content to include the new release. The repository is located at https://github.com/apache/thrift-website and there are plenty of instructions how to update both staging and live web site. With regard to the release, its actually quite simple: check out the main branch and editing two lines in _config.yml, then commit. The build bot will update staging. After checking everything is right, simply fast-forward "asf-site" to "asf-staging" and push, then production sit [...]
 
 1. Make an announcement on the dev@ and user@ mailing lists of the release.  There's no template to follow, but you can point folks to the official web site at https://thrift.apache.org, and to the GitHub site at https://github.org/apache.thrift.