-
Notifications
You must be signed in to change notification settings - Fork 4
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
hex package #3
Comments
Ah, I see: experimentation on master with the stable code (v1.0) on a branch. I've done the opposite: the experimentation is on the branch v2.0, and when I feel it is ready I will merge that into master and master will contain the v2.0 code. |
I think what you suggest makes sense. When the time is right, I'll create a branch off of master and call that v1.0.0. Then I will merge the new code into master, create a v2.0.0 branch for this new code, and publish that to Hex. |
great idea, that suggestion resolve the problem. |
do you want help to resolve that ?? |
Thank you for the offer, but no. I'm just waiting to see if any more comments trickle in. I'll probably merge the 2.0 into master and create the new v2.0.0 branch tonight or tomorrow. I'll then push to hex so that CSVLixir 2.0.0 is generally available. Thanks again for your offer of help. |
i saw in https://hex.pm/packages/csvlixir don't have 2.0.
In other projets, for example elixir the branch master, is the new features, and old version have a branch.
for example, I'm a new developper in the project, i don´t now this diferente using on the branch.
do you like change de master branch to 2.0 ??
The text was updated successfully, but these errors were encountered: