GitHub user mike-jumper opened a pull request:
https://github.com/apache/incubator-guacamole-website/pull/44
Release 0.9.13-incubating.
This change marks 0.9.13-incubating as released, and updates the top-level
symbolic links to the latest documentation.
We'll still need to hold off on actually *deploying* these changes until
2017-08-01 00:01 -0700, as that will be 24 hours since the release artifacts
were deployed (and the mirrors need roughly 24 hours to sync). From
http://www.apache.org/dev/release.html#release-announcements:
> Please ensure that you wait at least 24 hours after uploading a new
release before updating the project download page and sending the announcement
email(s). This is so that mirrors have sufficient time to catch up. (For
time-critical security releases, the download pages script supports bypassing
this requirement.)
Also, from http://www.apache.org/dev/release-publishing.html#sync-delay:
> Apache uses svnpubsub internally and rsync mirrroring externally. Files
committed to the Subversion repository at https://dist.apache.org/repos/dist/
are automatically copied, using svnpubsub, to www.apache.org , and then the
external mirrors pick up the files from www.apache.org. It may take up to 24
hours or more for a newly published release to be sync'd to all mirrors.
Mirrors have their own schedules. [Mirrors are
required](http://www.apache.org/info/how-to-mirror.html#Requirements) to check
at least once a day, but most will check for updates 2 to 4 times per day.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mike-jumper/incubator-guacamole-website
publish-release
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-guacamole-website/pull/44.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #44
----
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
