[jira] [Created] (GUACAMOLE-692) Update release layout to allow compliance with updated ASF policy

2019-01-09 Thread Michael Jumper (JIRA) 
Michael Jumper created GUACAMOLE-692:


 Summary: Update release layout to allow compliance with updated 
ASF policy
 Key: GUACAMOLE-692
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-692
 Project: Guacamole
  Issue Type: Task
  Components: Website
Reporter: Michael Jumper


The [latest version of the ASF release 
policy|https://www.apache.org/dev/release-distribution#sigs-and-sums], as 
updated early/mid last year, specifies that releases:

# Should no longer include MD5 checksums
# Should now use the {{.sha256}} extension for SHA-256 checksums (rather than 
the old {{.sha}} extension).
# May provide SHA-512 checksums with the extension {{.sha512}}.
# Must provide SHA-256, SHA-512, or both.

While continuing to use MD5 and SHA-256 with the legacy extension is still 
technically compliant, we should update the website build such that we can 
provide the recommend, non-legacy checksums in future releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (GUACAMOLE-692) Update release layout to allow compliance with updated ASF policy

2019-01-09 Thread Michael Jumper (JIRA) 


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jumper reassigned GUACAMOLE-692:


Assignee: Michael Jumper

> Update release layout to allow compliance with updated ASF policy
> -
>
> Key: GUACAMOLE-692
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-692
> Project: Guacamole
>  Issue Type: Task
>  Components: Website
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Blocker
>
> The [latest version of the ASF release 
> policy|https://www.apache.org/dev/release-distribution#sigs-and-sums], as 
> updated early/mid last year, specifies that releases:
> # Should no longer include MD5 checksums
> # Should now use the {{.sha256}} extension for SHA-256 checksums (rather than 
> the old {{.sha}} extension).
> # May provide SHA-512 checksums with the extension {{.sha512}}.
> # Must provide SHA-256, SHA-512, or both.
> While continuing to use MD5 and SHA-256 with the legacy extension is still 
> technically compliant, we should update the website build such that we can 
> provide the recommend, non-legacy checksums in future releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (GUACAMOLE-693) Update copyright year to 2019

2019-01-09 Thread Michael Jumper (JIRA) 
Michael Jumper created GUACAMOLE-693:


 Summary: Update copyright year to 2019
 Key: GUACAMOLE-693
 URL: https://issues.apache.org/jira/browse/GUACAMOLE-693
 Project: Guacamole
  Issue Type: Task
  Components: Documentation, guacamole-client, guacamole-server, Website
Reporter: Michael Jumper


Happy New Year! At the beginning of each year, the copyright statements in the 
{{NOTICE}} files and website footer must be updated. They {{NOTICE}} files 
currently state:

{quote}
Apache Guacamole
Copyright 2018 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
{quote}

The year needs to be updated to 2019. Similar changes must be made to the 
website footer.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (GUACAMOLE-692) Update release layout to allow compliance with updated ASF policy

2019-01-09 Thread Michael Jumper (JIRA) 


 [ 
https://issues.apache.org/jira/browse/GUACAMOLE-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jumper resolved GUACAMOLE-692.
--
Resolution: Done

> Update release layout to allow compliance with updated ASF policy
> -
>
> Key: GUACAMOLE-692
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-692
> Project: Guacamole
>  Issue Type: Task
>  Components: Website
>Reporter: Michael Jumper
>Assignee: Michael Jumper
>Priority: Blocker
>
> The [latest version of the ASF release 
> policy|https://www.apache.org/dev/release-distribution#sigs-and-sums], as 
> updated early/mid last year, specifies that releases:
> # Should no longer include MD5 checksums
> # Should now use the {{.sha256}} extension for SHA-256 checksums (rather than 
> the old {{.sha}} extension).
> # May provide SHA-512 checksums with the extension {{.sha512}}.
> # Must provide SHA-256, SHA-512, or both.
> While continuing to use MD5 and SHA-256 with the legacy extension is still 
> technically compliant, we should update the website build such that we can 
> provide the recommend, non-legacy checksums in future releases.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)