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

DOC: adding artefact retention policy to SPEC4 #262

Merged
merged 2 commits into from
Aug 17, 2023

Conversation

bsipocz
Copy link
Member

@bsipocz bsipocz commented Aug 16, 2023

This is to address #261
I'm on the opinion that it was a mistake to include so much implementation detail in the SPEC itself, but as the other specifics of https://anaconda.org/scientific-python-nightly-wheels are in the docs, we should list these policies, too.

Also note, that we may eventually change the actual numbers, e.g. scientific-python/upload-nightly-action#35

cc @mattip

@mattip
Copy link
Contributor

mattip commented Aug 16, 2023

Thanks, LGTM (I had to look up artefact to discover it is the British spelling of the American artifact)

spec-0004/index.md Outdated Show resolved Hide resolved
@jarrodmillman
Copy link
Member

Should we leave the actual numbers out of the SPEC? I think it is sufficient to mention there is a limit and that you can find it in the action. Just trying to keep the actual SPEC documents short and reduce the amount of places we need to update things if they change.

@bsipocz
Copy link
Member Author

bsipocz commented Aug 16, 2023

Should we leave the actual numbers out of the SPEC? I think it is sufficient to mention there is a limit and that you can find it in the action. Just trying to keep the actual SPEC documents short and reduce the amount of places we need to update things if they change.

Yep, I like that, and will update it in the text.

@jarrodmillman jarrodmillman merged commit 18feb0c into scientific-python:main Aug 17, 2023
1 check passed
@bsipocz bsipocz deleted the SPEC4_cleanup_policy branch August 18, 2023 00:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants