Skip to content

Create tag for all stable releases when they are phased out. #64

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

Closed
Ali-Khatami opened this issue Apr 3, 2013 · 3 comments
Closed

Create tag for all stable releases when they are phased out. #64

Ali-Khatami opened this issue Apr 3, 2013 · 3 comments
Assignees
Milestone

Comments

@Ali-Khatami
Copy link
Contributor

With the latest release of 1.1.1 and a 1.2-wip branch already being worked on it seems like moving forward a tag should be created for all stable releases when they are phased out. This way developers who have yet to upgrade or feel they can not upgrade (for what ever reason) will be able to review docs and can find their stable version. Also, it will provide better history, bug tracking, etc as the framework evolves.

Ideally we would have a tag for each stable release <major>.<minor>.<patch>, but if that becomes obnoxious it would be nice to at least have a tag for <major>.<minor>.<last_patch>

@brianbaker
Copy link
Member

The build script does have the --release flag which will create a tag based on the version. I think we just need to make sure to do that when releasing a new version.

It probably wouldn't be bad to go back and tag the previous releases as well.

@ghost ghost assigned brianbaker Apr 4, 2013
@brianbaker
Copy link
Member

Tags for past revisions have been created. https://github.com/OpenF2/F2/tags

@markhealey
Copy link
Member

Nice work!

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