Download page improvements/rework (was Re: Release related Issues created by INFRA)

2021-03-24 Thread David Blevins
> On Mar 24, 2021, at 12:40 AM, Richard Zowalla wrote: > > I have merged the "manual" changes to add the missing links to the .asc > files of the release download page. > > In this process, I discovered, that we are not using the Downloads > generator class [2] anymore. My questions is: > >

Re: Release related Issues created by INFRA

2021-03-24 Thread Jonathan Gallimore
On Wed, Mar 24, 2021 at 9:17 PM David Blevins wrote: > Thanks or pushing this back up to the top. Some thoughts below. > I had just come here to say the same thing - thank you Richard! > > > On Mar 24, 2021, at 12:46 AM, Richard Zowalla wrote: > > > > It seems, we are already providing

Re: Release related Issues created by INFRA

2021-03-24 Thread David Blevins
Thanks or pushing this back up to the top. Some thoughts below. > On Mar 24, 2021, at 12:46 AM, Richard Zowalla wrote: > > It seems, we are already providing SHA256/SHA512 checksums for newer > releases. To rephrase my comment: If we would switch to Maven > repository links instead, we would

[GitHub] [tomee-site-generator] rzo1 edited a comment on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 edited a comment on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806034405 I think, we first need to switch back to an automated way of generating this page again :smile: - too many hard structural changes would lead to some error prone

[GitHub] [tomee-site-generator] rzo1 edited a comment on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 edited a comment on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806034405 I think, we first need to switch back to an automated way of generating this page again :smile: - too many hard structural changes would lead to some error prone

[GitHub] [tomee-site-generator] sebbASF commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
sebbASF commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806038039 N.B. closer.cgi cannot be used for PGP or SHA files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [tomee-site-generator] rzo1 commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806034405 I think, we first need to switch back to an automated way of generating this page again :smile: - too many hard structural changes would lead to some error prone CnP

[GitHub] [tomee-site-generator] rmannibucau commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rmannibucau commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806024035 If it helps: Name and Type/Download columns can be merged, no point to have "ZIP" or "TAR GZ" text alone, so I would merge the download link with the name

[GitHub] [tomee-site-generator] rzo1 commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806020740 > The download page "Links" column is getting a bit messy; it would be easier to use if there were 2 separate columns for the sigs and hashes (SHA256 + 512). > >

[GitHub] [tomee-site-generator] sebbASF commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
sebbASF commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-806009958 The download page "Links" column is getting a bit messy; it would be easier to use if there were 2 separate columns for the sigs and hashes (SHA256 + 512).

[GitHub] [tomee] rzo1 commented on pull request #765: TOMEE-2976 - Provide two examples using Arquillian & JUnit 5

2021-03-24 Thread GitBox
rzo1 commented on pull request #765: URL: https://github.com/apache/tomee/pull/765#issuecomment-805784199 @cesarhernandezgt The failing tests in https://ci-builds.apache.org/job/Tomee/job/pull-request/132/ seem unrelated to me. Is this a Jenkins issue? wdyt? -- This is an automated

Re: Release related Issues created by INFRA

2021-03-24 Thread Richard Zowalla
Hi, wanted to raise attention on this mail again: I have merged the "manual" changes to add the missing links to the .asc files of the release download page. In this process, I discovered, that we are not using the Downloads generator class [2] anymore. My questions is: Did we switch on

[GitHub] [tomee-site-generator] rzo1 merged pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 merged pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service,

[GitHub] [tomee-site-generator] rzo1 commented on pull request #21: TOMEE-2975 - Download page must provide sigs for all release artifacts

2021-03-24 Thread GitBox
rzo1 commented on pull request #21: URL: https://github.com/apache/tomee-site-generator/pull/21#issuecomment-805569951 I will merge it now (to fix it short term) - as the links are "manually" validated. The discussion related to mirrors vs central is now on the mailing list [1]. I will