Skip to content

Conversation

@slawekjaranowski
Copy link
Member

Following this checklist to help us incorporate your
contribution quickly and easily:

  • Make sure there is a JIRA issue filed
    for the change (usually before you start working on it). Trivial changes like typos do not
    require a JIRA issue. Your pull request should address just this issue, without
    pulling in other changes.
  • Each commit in the pull request should have a meaningful subject line and body.
  • Format the pull request title like [MEAR-XXX] - Fixes bug in ApproximateQuantiles,
    where you replace MEAR-XXX with the appropriate JIRA issue. Best practice
    is to use the JIRA issue title in the pull request title and in the first line of the
    commit message.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Run mvn clean verify to make sure basic checks pass. A more thorough check will
    be performed on your pull request automatically.
  • You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

@slawekjaranowski
Copy link
Member Author

Now looks as

image

@slawekjaranowski
Copy link
Member Author

Next proposition:

image

Inspired by ASF download template: https://www.apache.org/dyn/closer.lua

@kwin
Copy link
Member

kwin commented Oct 11, 2022

Still not convinced TBH ;-). Integrity is usually checked by Maven Resolver, only authenticity needs to be verified manually.

@michael-o
Copy link
Member

Still not convinced TBH ;-). Integrity is usually checked by Maven Resolver, only authenticity needs to be verified manually.

I agree here. There is a clear distinction between checksum and a signature.

@slawekjaranowski
Copy link
Member Author

It is download page where we put link to source release of project from ASF distribution area - it is not binary version of plugin which is downloaded by Maven.

Users download it manually and we give instruction how to verify it.

@michael-o
Copy link
Member

michael-o commented Oct 11, 2022

It is download page where we put link to source release of project from ASF distribution area - it is not binary version of plugin which is downloaded by Maven.

Users download it manually and we give instruction how to verify it.

If so, we should require to the check the signature only, not the checksum since sig check will include checksum.

@slawekjaranowski
Copy link
Member Author

There is linked ASF instruction https://www.apache.org/info/verification.html - which describe both methods
Also at page https://infra.apache.org/release-download-pages.html we have information that both should be present - checksum and signature

@michael-o
Copy link
Member

michael-o commented Oct 11, 2022

Me and @cstamas have expressed many times that this ASF page requires a cleanup because it mixes hashes and checksums throughout. It starts with hashes, then talks about checksums.

@michael-o
Copy link
Member

This statement is wrong:

The checksum of a file is a fixed length string, that (in practice) uniquely identifies the contents of the file. 

@slawekjaranowski
Copy link
Member Author

ok, my goal was a refresh a little download page, remove broken links to mirrors

changing ASF release policy and related documents are out of scope for this PR 😄

Copy link
Member

@michael-o michael-o left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Last nit and then we can merge

@michael-o
Copy link
Member

ok, my goal was a refresh a little download page, remove broken links to mirrors

changing ASF release policy and related documents are out of scope for this PR 😄

I know and I appreciate that. It is a different discussion which has been bugigng me for quite some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants