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

reorganize stable branch and download tags? #7

Closed
JonnyJD opened this issue Feb 6, 2012 · 3 comments
Closed

reorganize stable branch and download tags? #7

JonnyJD opened this issue Feb 6, 2012 · 3 comments

Comments

@JonnyJD
Copy link
Owner

JonnyJD commented Feb 6, 2012

1f7fa42 fixed the first regression (some single disc releases had unnecessary offset questions)

So having master as completely stable branch did not work?
Maybe I should work on dev branches between releases?

Especially because https://github.com/JonnyJD/musicbrainz-isrcsubmit/raw/master/isrcsubmit.py would be a nice "latest stable" download link.
Another option is to create a stable branch, but since master is the default, this might not be optimal.

Note, that also, that https://raw.github.com/JonnyJD/musicbrainz-isrcsubmit/v0.2.4/isrcsubmit.py is a valid download for 0.2.4.

The github integrated download (for tags) is not really usefull, by the way.

@JonnyJD
Copy link
Owner Author

JonnyJD commented Feb 6, 2012

On the other hand, I just added a individual download: https://github.com/downloads/JonnyJD/musicbrainz-isrcsubmit/isrcsubmit.py

This is directly taken from http://kraehen.org/isrcsubmit.py

Github tells me and everybody how often the files were downloaded (without me checking my server logs).
However there is no such thing as a symlink. When the new version comes, I have to delete and recreate.
I also added a stable https://github.com/downloads/JonnyJD/musicbrainz-isrcsubmit/isrcsubmit-0.2.4.py.
Altogether, since you can also just download the script straight from the repo (see above), the download count here is not telling much anyways.

@JonnyJD
Copy link
Owner Author

JonnyJD commented Feb 6, 2012

Additionally I should use annotated tags (git tag -a) or even signed tags, although github does not care at all.

@JonnyJD
Copy link
Owner Author

JonnyJD commented Mar 7, 2012

This is basically fixed. We have a myriad of download options and master is now somewhat stable, using feature branches for bigger changes. The tags are signed with git tag -u <keyname/mail> v0.x.

@JonnyJD JonnyJD closed this as completed Mar 7, 2012
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

1 participant