Repository: sling-site Updated Branches: refs/heads/master 3a0a7c336 -> d0465e8f4
clarify how to update the downloads page Project: http://git-wip-us.apache.org/repos/asf/sling-site/repo Commit: http://git-wip-us.apache.org/repos/asf/sling-site/commit/d0465e8f Tree: http://git-wip-us.apache.org/repos/asf/sling-site/tree/d0465e8f Diff: http://git-wip-us.apache.org/repos/asf/sling-site/diff/d0465e8f Branch: refs/heads/master Commit: d0465e8f4ec3c391c2d26a7c3fd933dfda9a806c Parents: 3a0a7c3 Author: Konrad Windszus <k...@apache.org> Authored: Sat Oct 7 12:55:21 2017 +0200 Committer: Konrad Windszus <k...@apache.org> Committed: Sat Oct 7 12:55:21 2017 +0200 ---------------------------------------------------------------------- .../jbake/content/documentation/development/release-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/sling-site/blob/d0465e8f/src/main/jbake/content/documentation/development/release-management.md ---------------------------------------------------------------------- diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md index 18dc465..186c9a4 100644 --- a/src/main/jbake/content/documentation/development/release-management.md +++ b/src/main/jbake/content/documentation/development/release-management.md @@ -196,7 +196,7 @@ If the vote passes: 1. Login to [https://repository.apache.org](https://repository.apache.org) with your Apache SVN credentials. Click on *Staging*. Find your closed staging repository and select it by checking the select box. Select the *Releases* repository from the drop-down list and click *Release* from the menu above. 1. Once the release is promoted click on *Repositories*, select the *Releases* repository and validate that your artifacts are all there. 1. Update the releases section on the website at [releases](/releases.html). -1. Update the download page on the website at [downloads](/downloads.cgi) to point to the new release. +1. Update the download page on the website at [downloads](/downloads.cgi) to point to the new release. For this you need to modify the [according Groovy Template](https://github.com/apache/sling-site/blob/master/src/main/jbake/templates/downloads.tpl). 1. If you think that this release is worth a news entry, update the website at [news](/news.html) For the last two tasks, it's better to give the mirrors some time to distribute the uploaded artifacts (one day should be fine). This ensures that once the website (news and download page) is updated, people can actually download the artifacts.
