-
Notifications
You must be signed in to change notification sett 8000 ings - Fork 70
make release
target
#761
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
Comments
Hey @joshmoore we've received some feedback that it has been hard for external developers to come back to starfish after a few weeks have elapsed and figure out what's happened. We're thinking about initiating to a release cycle (maybe bi-weekly?) to help mitigate this. Would you be interested in creating this make target? If you build it, we'll commit to using it every weeks, and having clear changelogs :-) |
Investigating. I'll post some thoughts ASAP. |
Ok. I have something that's mostly working based on
If there are any preliminary objections to that, now would be a good time to express them. The general release process would be:
If there are any issues, the commands need to be rolled back last to front:
|
There are some who have moved away from pbr: other options for the version calculation:
|
Looks like you provided your own objection 😆 No problems here, very interested to see what you come up with! |
Heh. It did "just work" (TM) for starfish, so I wouldn't be opposed to rolling back to it and dropping versioneer. Probably need a discussion around all of this. |
I just read this (I suck). I understand #1059 much better now. :) |
🤣 (I looked for a place to put this content since it will be useful but didn't find anything definitive. Preferences?
|
see: #709 (comment)
Potential sequence:
sdist
, install, and test with the installation:run(no longer complicated)get_git_commit_hash
tests etc. (see Add to provenance log #968)generate and push commit to bioconda-recipes (and potentially open a PR)(happens automatically now on tagging)add .dev to version number, commit, and push to master(not needed with versioneer)Similar checklist for comparison:
Other things to consider:
The text was updated successfully, but these errors were encountered: