-
-
Notifications
You must be signed in to change notification settings - Fork 849
Releasing 1.15.0 #728
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
Would this be a release of current master? #641 was arguing that it needed to be a major version bump. That said, 👍 for a new release. |
I had a look at the commit since the last pre-release and are mostly bug fixes or docs addition. What made you think we need to bump to release the current master? Any particular commit/PR? Thanks! |
The open PR (not mine) has argumentation. I don't have a strong opinion other than that it's time for a new release :) |
I'm not going to merge them before releasing 1.15.0 :) |
When could we release the v1.15? Or I have to use a workaround like |
There is work undergoing to release it in the coming days! |
The repo is ready for the 1.15.0. I need to build and release the gem, and we're set! |
when can you release for gem? can't wait |
Released |
Hi @skywinder , @olleolleolle
We have a number of issues asking for a new release (#722, #649) and issues that are blocked because they need a new release (#717).
I think we should release the 1.15.0 final, pointing to the latest master (the latest commits add nothing major).
I think this is a must to start cleaning the issue backlog. We want to ask the issue reporters to try with the latest released version. Eventual fixes will be handled by releasing minor versions.
Thoughts?
Questions:
Tasks:
The text was updated successfully, but these errors were encountered: