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

Please tag releases #1

Closed
tillea opened this issue Oct 27, 2022 · 2 comments
Closed

Please tag releases #1

tillea opened this issue Oct 27, 2022 · 2 comments

Comments

@tillea
Copy link

tillea commented Oct 27, 2022

Hi,
I intend to update the Debian package of a bioinformatics application (minimac4). It says in its requirements.txt:

jonathonl/omp@522849581eb900a8bce9621a557ef1cadf600441

In Debian we need to package external dependencies and we like to provide users with real releases instead of "random" development commits. It turns out that the required commit is the last in your develop branch and I verified that this commit is really needed since minimac4 does not build with latest HEAD. It would be great if you could

  1. merge develop to master
  2. tag this commit as release

This would give us some confidence that this code is somehow tested and verified when we create a Debian package from it.
Thanks a lot in advance, Andreas.

@jonathonl
Copy link
Owner

This has been done. See https://github.com/jonathonl/omp/releases/tag/v1.0.0.

@tillea
Copy link
Author

tillea commented Oct 28, 2022 via email

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