-
Notifications
You must be signed in to change notification settings - Fork 202
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
Why no releases since Feb? #65
Comments
👍 |
5 similar comments
👍 |
+1 |
+1 |
+1 |
+1 |
Cut a release, need to keep momentum. If your worried about breaking, do a release candidate. Happy to run our jobs here with that to flush out any issues. |
+1 @Jimflip's comment |
👍 |
@fnichol Still no new release? Theres a lot of changes in the new ec2 plugin that we're waiting for. Is there a specific reason that you're holding off? |
Ping other maintainers @schisamo @sethvargo |
Ohai everyone 😄! I get a GitHub notification and an email for every comment that occurs on this thread. We are not ignoring you, but continuously 👍ing an issue is super annoying. If you really need to run off master, you can clone and run |
Sorry! @fnichol is there an ETA on a release? |
I ran into the same problem and installed HEAD from the master branch to get some bugfixes I needed. You can add it the following way (if you do not know how). Exchange
|
If you add a So locally I added a Gemfile to my test cookbook, I'm also working on getting a release for kitchen-ec2 ready, but I want to refactor the code before I do that. It may not happen until after ChefConf 😞 |
👍 |
1 similar comment
👍 |
I just released kitchen-ec2 version 0.9.0 - please check it out! I deprecated some configs (affected ones can be seen in the README) but they will continue to work until version 1.0.0. My current roadmap is to release a 0.10.0 version which adds windows support. Then I will release a 1.0.0 which removes the deprecated configs and pulls in any remaining bug fixes. |
👍 Tank you @tyler-ball keep up the great work!! |
Lots of useful new features in master right now but the last release was in Feb. What happened to continuous deployment? Any plans to cut a release in the near future?
The text was updated successfully, but these errors were encountered: