[ci/cd] release schedule on pypi

[xgui3783]

I would like to ask what would be a good release schedule, so that the package on pypi can be updated regularly? (probably not good to wait until users poke us, but something tangible like once a month? In other projects I am involved in, we have different practices)

I would also like to create an github action where, on new release created, it will create a release on pypi (likey adopting what we are doing with siibra-python (https://github.com/FZJ-INM1-BDA/siibra-python/blob/main/.github/workflows/pyblish-release-to-pypi.yml) )

Would love to hear your opinion @apdavison

[apdavison]

I think this is a "burst-of-activity-followed-by-months-of-quiet"-type project, so I don't think a regular release schedule would make sense; rather we should make a release after every significant change (but perhaps not more often than one release per week?)

If you have experience with setting up such a workflow, @xgui3783, please go ahead.

[xgui3783]

I agree with release when there has been a burst of activities.

I will work on ci/cd pipeline that pushes to pypi on release

[xgui3783]

should be partially fixed #44

next steps seems to require access to github action environment, per https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing and https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments#creating-an-environment

I do not seem to have access to https://github.com/HumanBrainProject/ebrains-storage/settings (I have the button on my UI, but I get Page not found when clicking it)

@apdavison do you have access to ebrains-storage setting page? If you neither, we will have to have one of the others to set up the rest =/

[apdavison]

Hi @xgui3783 : I've just given you access, please try again

[xgui3783]

Yup works now, thanks!

[xgui3783]

hmm bad news. I couldn't find "environments" tab, and according to https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments#about-environments , humanbrianproject might be on a legacy plan, and will not have access to enviornments.

@apdavison you might know how humanbrainproject org on github is setup?

Also, what's your opinion on just setting a script and upload the artefact with for example twine?

[apdavison]

it looks as though humanbrainproject is on a legacy Gold plan

uploading via twine seems ok with me, and/or we can do the PyPI release via the EBRAINS GitLab mirror

[xgui3783]

it appears gitlab release to pypi uses twine any way:

https://docs.gitlab.com/user/packages/pypi_repository/auto_publish_tutorial/

I will create PR and ping you when ready for review

[xgui3783]

fixed by #45