[jira] [Reopened] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened GROOVY-7779: -- groovy/4.0.0-rc-2/ does not appear to be needed any more > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Assignee: Paul King >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Reopened] (GROOVY-9846) Spurious hashes and sigs for 2.4.1 on download page
[ https://issues.apache.org/jira/browse/GROOVY-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened GROOVY-9846: -- I think there's still a problem. The archive server is not to be used for serving current releases, and I don't think it should be used for their hashes and sigs either because we don't want to encourage its use for current releases. Given that the page only lists current releases, why are the archive links even needed? > Spurious hashes and sigs for 2.4.1 on download page > --- > > Key: GROOVY-9846 > URL: https://issues.apache.org/jira/browse/GROOVY-9846 > Project: Groovy > Issue Type: Bug >Reporter: Sebb >Assignee: Paul King >Priority: Major > > The download page > https://groovy.apache.org/download.html > has two sets of sigs and hashes for version 2.4.1 for all but the source > bundle. > These are prefixed with DIST: and PERM: but have identical links. > Rather confusing for downloaders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GROOVY-9846) Spurious hashes and sigs for 2.4.1 on download page
Sebb created GROOVY-9846: Summary: Spurious hashes and sigs for 2.4.1 on download page Key: GROOVY-9846 URL: https://issues.apache.org/jira/browse/GROOVY-9846 Project: Groovy Issue Type: Bug Reporter: Sebb The download page https://groovy.apache.org/download.html has two sets of sigs and hashes for version 2.4.1 for all but the source bundle. These are prefixed with DIST: and PERM: but have identical links. Rather confusing for downloaders. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GROOVY-9458) Missing sigs and hashes on download page
[ https://issues.apache.org/jira/browse/GROOVY-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17079633#comment-17079633 ] Sebb commented on GROOVY-9458: -- The download page links to https://dl.bintray.com/groovy/Distributions/groovy-3.0.2.msi. This is a download artifact / package, and is linked from the download page so must have a sig and a hash. If you disagree, please raise this with Infra and/or Legal so the rules can be clarified (if necessary). > Missing sigs and hashes on download page > > > Key: GROOVY-9458 > URL: https://issues.apache.org/jira/browse/GROOVY-9458 > Project: Groovy > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The public download page includes links to several Windows installer > executables. > These have neither signatures nor hashes. > However as per [1] > "All supplied packages MUST be cryptographically signed by the Release > Manager with a detached signature" > And as per [2] > "For every artifact distributed to the public through Apache channels, the > PMC ... MUST supply at least one checksum file" > Please either remove the links or provide the required sigs and hashes. > Thanks. > [1] http://www.apache.org/legal/release-policy.html#release-signing > [2] https://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GROOVY-9458) Missing sigs and hashes on download page
[ https://issues.apache.org/jira/browse/GROOVY-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17072691#comment-17072691 ] Sebb commented on GROOVY-9458: -- My reading of the cited pages is that the rules apply to all packages, regardless of origin. If you disagree with this, I suggest you ask for clarification from the page owners. > Missing sigs and hashes on download page > > > Key: GROOVY-9458 > URL: https://issues.apache.org/jira/browse/GROOVY-9458 > Project: Groovy > Issue Type: Bug >Reporter: Sebb >Priority: Major > > The public download page includes links to several Windows installer > executables. > These have neither signatures nor hashes. > However as per [1] > "All supplied packages MUST be cryptographically signed by the Release > Manager with a detached signature" > And as per [2] > "For every artifact distributed to the public through Apache channels, the > PMC ... MUST supply at least one checksum file" > Please either remove the links or provide the required sigs and hashes. > Thanks. > [1] http://www.apache.org/legal/release-policy.html#release-signing > [2] https://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GROOVY-9458) Missing sigs and hashes on download page
Sebb created GROOVY-9458: Summary: Missing sigs and hashes on download page Key: GROOVY-9458 URL: https://issues.apache.org/jira/browse/GROOVY-9458 Project: Groovy Issue Type: Bug Reporter: Sebb The public download page includes links to several Windows installer executables. These have neither signatures nor hashes. However as per [1] "All supplied packages MUST be cryptographically signed by the Release Manager with a detached signature" And as per [2] "For every artifact distributed to the public through Apache channels, the PMC ... MUST supply at least one checksum file" Please either remove the links or provide the required sigs and hashes. Thanks. [1] http://www.apache.org/legal/release-policy.html#release-signing [2] https://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558522#comment-16558522 ] Sebb commented on GROOVY-7779: -- re: 2.4.15 - OK Sigs and hashes for current releases must have links that point to https://www.apache.org/dist/... Please fix that. Only use the archive server for archived releases. > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Assignee: Paul King >Priority: Major > Fix For: 2.4.15 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558284#comment-16558284 ] Sebb commented on GROOVY-7779: -- The links for sigs and hashes for 2.4.15 point to archive.apache.org, so I assumed that the release was not current. Are there plans for 2.4.16? If not, then it is nor current. All PMC members have write access to https://dist.apache.org/repos/dist/release/groovy/ so you should be able to delete the old directories, e.g. svn rm -m "Archive" https://dist.apache.org/repos/dist/release/groovy/2.5.0 > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Assignee: Paul King >Priority: Major > Fix For: 2.4.15 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened GROOVY-7779: -- There are still several old releases under dist/release: 2.4.15/ 2.5.0/ 2.6.0-alpha-3/ 3.0.0-alpha-1/ 3.0.0-alpha-2/ Please tidy these up. > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Assignee: Paul King >Priority: Major > Fix For: 2.4.15 > > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GROOVY-8550) Site does not display properly when using https:
Sebb created GROOVY-8550: Summary: Site does not display properly when using https: Key: GROOVY-8550 URL: https://issues.apache.org/jira/browse/GROOVY-8550 Project: Groovy Issue Type: Bug Reporter: Sebb As the subject says: https://groovy.apache.org/ does not display properly. This seems to be because some resources are unconditionally accessed via http: -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417360#comment-16417360 ] Sebb commented on GROOVY-7779: -- Ah, OK. I only checked the doc file mentioned in the initial reply. > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16417059#comment-16417059 ] Sebb commented on GROOVY-7779: -- Thanks, that's a lot better. The release guide has yet to be updated however. > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Priority: Major > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GROOVY-7779) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/GROOVY-7779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15180213#comment-15180213 ] Sebb commented on GROOVY-7779: -- A good time to remove an old release is when you send the Announce mail for a new one. By then the new release will presumably have been successfull deployed > Please delete old releases from mirroring system > > > Key: GROOVY-7779 > URL: https://issues.apache.org/jira/browse/GROOVY-7779 > Project: Groovy > Issue Type: Improvement > Components: release >Affects Versions: 2.4.5 > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > i.e. the ones listed as affected. > Thanks! > Also, if you have a release guide, perhaps you could add a cleanup stage to > it? > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GROOVY-7779) Please delete old releases from mirroring system
Sebb created GROOVY-7779: Summary: Please delete old releases from mirroring system Key: GROOVY-7779 URL: https://issues.apache.org/jira/browse/GROOVY-7779 Project: Groovy Issue Type: Improvement Components: release Affects Versions: 2.4.5 Environment: https://dist.apache.org/repos/dist/release/groovy/ Reporter: Sebb To reduce the load on the ASF mirrors, projects are required to delete old releases [1] Please can you remove all non-current releases? i.e. the ones listed as affected. Thanks! Also, if you have a release guide, perhaps you could add a cleanup stage to it? [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GROOVY-7743) Download page must link to ASF mirrors for sources
[ https://issues.apache.org/jira/browse/GROOVY-7743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb reopened GROOVY-7743: -- The source download link is wrong; it is missing the path segment 2.4.6/sources/ > Download page must link to ASF mirrors for sources > -- > > Key: GROOVY-7743 > URL: https://issues.apache.org/jira/browse/GROOVY-7743 > Project: Groovy > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/groovy/ >Reporter: Sebb >Assignee: Pascal Schumacher >Priority: Blocker > > The ASF requires that projects release source through the ASF mirror system > [1] > However I could not find any links to the source from the website. > [1] http://www.apache.org/dev/release-publishing.html#distribution -- This message was sent by Atlassian JIRA (v6.3.4#6332)
