[GitHub] guacamole-website pull request #65: Release 1.0.0.

2019-01-08 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/guacamole-website/pull/65


---


[GitHub] guacamole-website pull request #65: Release 1.0.0.

2019-01-08 Thread mike-jumper
GitHub user mike-jumper opened a pull request:

https://github.com/apache/guacamole-website/pull/65

Release 1.0.0.

This change marks 1.0.0 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 
2019-01-09 19:52:02 -0800, 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/guacamole-website release-1.0.0

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/guacamole-website/pull/65.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 #65


commit 3f8f3ca914ff1efed5ae76d3a97685fc6333a8ae
Author: Michael Jumper 
Date:   2019-01-09T04:45:01Z

Mark 1.0.0 as released.

commit 1379d00dc6194c4812d2a5da197b6623a7e99d51
Author: Michael Jumper 
Date:   2019-01-09T04:46:10Z

Update top-level symbolic links to point to 1.0.0 documentation.




---