-
Notifications
You must be signed in to change notification settings - Fork 533
Create the 1.6.0 release #434
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
Prerelease 1.6.0.pre1 was released and pushed to rubygems.org See https://github.com/ruby-git/ruby-git/releases/tag/v1.6.0.pre1 How does it sound to push a real 1.6.0 release in a week on Monday, Jan 27th? |
👍🏻 Works for me |
any updates? isn't it scheduled on Jan 27? |
Ping @jcouball 🙂 |
Thank you @TLiu2121999 for the reminder to give an update here. This week, I have been working through issue #418 because I wanted to make sure it wasn't caused by #405 (a new change introduced in 1.6.0.pre1). I believe that we have decided that it was not caused by #405 so I believe we are good to go with a new release. I will get to it as soon as possible. |
Created PR #443 for Release v1.6.0 |
The git gem version v1.6.0 has been released! |
Subject of the issue
Create the 1.6.0 release, the first release since August 18th, 2018.
Since it has been so long, the maintainers have decided to create a pre-release (1.6.0.pre1) with the pending changes. The maintainers will need to determine criteria for releasing a proper 1.6.0 release and put it in this issue so that people will know what to expect.
The text was updated successfully, but these errors were encountered: