Skip to content
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

Provide releases more often #1592

Closed
dvishniakov opened this issue Sep 5, 2017 · 3 comments
Closed

Provide releases more often #1592

dvishniakov opened this issue Sep 5, 2017 · 3 comments
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com.

Comments

@dvishniakov
Copy link

Terraform Version

0.10.x

It's not possible to point terraform to the commit of a provider (AFAIK). Can you release it more often? There are changes and bug fixes which people wait but it's not clear how to get them.
Also, by releasing more often it will be easier to bisect when a regression was introduced

@Ninir Ninir added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 6, 2017
@leftathome
Copy link

+1 for this, I'm doing some encrypted-EFS module development, so a release would save me some time modifying my CI pipeline to use an unreleased plugin.

Is there something the community could do to make it easier to release more frequently? More maintainers/reviewers, more comprehensive test coverage, improved release automation?

@radeksimko radeksimko added question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com. and removed enhancement Requests to existing resources that expand the functionality or scope. labels Oct 27, 2017
@bflad
Copy link
Contributor

bflad commented Apr 21, 2018

Previously we were doing a two-week release cadence. We're currently trying a weekly release cadence. At a certain point, we may provide nightly builds and potentially bake that mechanism into Terraform core, but there is no roadmap issue or timeline for that functionality in either core or the AWS provider. If you would like commit or automated nightly build support, I would suggest creating a separate issue and trying to gather 👍 upvotes on the original issue comment of that new issue to gain priority.

Given there is not a definition of done for this issue though, I'm going to close it. 😃

@bflad bflad closed this as completed Apr 21, 2018
@ghost
Copy link

ghost commented Apr 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question A question about existing functionality; most questions are re-routed to discuss.hashicorp.com.
Projects
None yet
Development

No branches or pull requests

5 participants