Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do we verify the artifacts after they are released? #8

Open
houshengbo opened this issue Apr 3, 2019 · 1 comment
Open

Do we verify the artifacts after they are released? #8

houshengbo opened this issue Apr 3, 2019 · 1 comment
Assignees

Comments

@houshengbo
Copy link

houshengbo commented Apr 3, 2019

Before the artifacts are moved into the release folder, they are still in staging status available under this link: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/. We should definitely verify them before the release. I THINK this is something the release-verification tool has already covered.

However, after we release them by copying the artifacts into the release directory, do we also need the verification? The release links are different. Although they are available under https://dist.apache.org/repos/dist/release/incubator/openwhisk/, we are only allowed to publish the mirror links, like https://www.apache.org/dyn/closer.lua?filename=incubator/openwhisk/apache-openwhisk-0.9.0-incubating/openwhisk-catalog-0.9.0-incubating-sources.tar.gz for the catalog.

Shall we make it possible to verify the artifacts after the release, like the ones at the mirror links?

We trust the all the artifacts when they are under dev with the release-verification. Do we take it for granted that they are trustworthy after they are copied to release? :-)

@jthomas jthomas self-assigned this Apr 3, 2019
@jthomas
Copy link
Owner

jthomas commented Apr 10, 2019

@houshengbo It is possible to modify the tool to also validate releases from the release as well as staging directories. Does anyone do this at the moment? I think we just trust it works... :)

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

No branches or pull requests

2 participants