Skip to content

Conversation

@bluetech
Copy link
Member

Fix #406

@bluetech bluetech force-pushed the releasing-pre-test branch from 9f4c799 to 2e2a040 Compare June 20, 2023 07:46
Release Procedure
-----------------

#. Dependening on the magnitude of the changes in the release, consider testing
Copy link
Member

Choose a reason for hiding this comment

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

Perhaps we should have a workflow which runs them all in parallel? This workflow can then be triggered manually and perhaps also in a cron and/or merge with main.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes that would be good, but I am too lazy to do that ATM, but wanted to at least make it possible to test locally for now.

@bluetech
Copy link
Member Author

BTW if you have other projects we might want to test, let me know. I know of airflow but I had some trouble setting it up.

@bluetech bluetech merged commit 3f9f622 into pytest-dev:main Jun 20, 2023
@bluetech bluetech deleted the releasing-pre-test branch June 20, 2023 16:41
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.

RELEASING: add pre-release suggestion to test downstream projects

2 participants