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 #116

Open
0xaf1f opened this issue Apr 22, 2016 · 2 comments
Open

Please tag releases #116

0xaf1f opened this issue Apr 22, 2016 · 2 comments
Assignees

Comments

@0xaf1f
Copy link

0xaf1f commented Apr 22, 2016

I am trying to update the Debian package for GenomicConsensus and see that it now depends on pbcommand >= 0.3.20. I have not updated the pbcommand package since 0.2.17 since that was the latest tagged release here. Alternatively, I can point our version tracker to PyPI. Is that a better place to retrieve the source code from? I otherwise have to figure out which commit corresponds to the latest PyPI release. It would be much appreciated if you could continue to tag releases as you have been doing up until 0.2.17.

@mpkocher
Copy link
Contributor

@natechols when we branch in perforce, can you cut a new release to pypi with the pbcommand version corresponding to the SA 3.1.0 ?

@0xaf1f
Copy link
Author

0xaf1f commented Apr 24, 2016

Thanks. In the meantime, I'll use 5939289 to update the package as 0.3.22 in Debian. I'd still really appreciate tags so I can tell when to make updates.

pacbbbbot pushed a commit that referenced this issue Aug 7, 2019
…condition-in-import-dataset-jobs to develop

* commit '1806df2424509eec02b9154a87c63f649f07c540':
  pep8 fix
  add new avoidDuplicateImport param to dataset import function
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

3 participants