-
Notifications
You must be signed in to change notification settings - Fork 767
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
[Proposal] Maintaining stable releases #70
Comments
YES! I've been thinking about the fact that we haven't tagged any releases, and that's something I'd like to change as it may help when it comes to handling issues in the future. I like the idea of a So our workflow would maybe look something like this?
|
@Stratus3D had the same thing in mind but without the first step (because we dont really know what's going to come next... being very honest :) ) So something like this:
@tuvistavie opinions? |
I totally agree on maintaining stable releases. I have no strong opinions on the workflow, but what are the For reference, in some other project I maintain, I simply tag each release,
|
I agree with @tuvistavie on having only a master branch with tagged releases. Maintaining a separate We could create a Homebrew formula that installs the latest tag, and have alternate instructions for non homebrew users. The |
I've tagged the first release (0.1.0) and I've prepared everything for the next release (it has to be 0.2.0 since we have some API changes). I also created a PR that updates the install command in the readme so that 0.1.0 is checked out when asdf is installed. I also created a separate PR that adds a change log, if you all thinks that is necessary. I think this is all that needs to be done to get the ball rolling for stable releases. From now on when creating a release we just need to:
We can also increment the version number in |
Closing this issue since I have merged both PRs. If anyone else has any thoughts or concerns on this please re-open this issue. |
There's an increase in fixes happening in the master branch.
Should we have a separate
stable
branch and release tags that are merged into thestable
branch? So whoever gets thestable
branch always gets the latest stable release AND can also pick a tag and use just that.The above idea above was just an opinion. Open to other ideas to maintain a stable release.
The text was updated successfully, but these errors were encountered: