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

New release? #486

Closed
AndreaGiardini opened this issue Sep 28, 2017 · 3 comments
Closed

New release? #486

AndreaGiardini opened this issue Sep 28, 2017 · 3 comments

Comments

@AndreaGiardini
Copy link

Hi there,

Last release is over one month old and during this time the provider has evolved a lot. Especially PR like this ( #25 ) have been merged and could overcome limitations of the current version.

Is there any reason not to publish a new release?

@paddycarver
Copy link
Contributor

The 1.0.0 & 1.0.1 releases just landed. I realise they had a lot of features people were waiting on, and apologise for the delay. To give some insight as to why the release wasn't just published, a lot of things went into the actual release process:

  • Making sure that the breaking changes we knew were on the horizon were actually merged, so we didn't release a 1.0.0 just to follow it with 2.0.0 a week later.
  • Removing the deprecated fields on resources that have been deprecated for a while, making our codebase smaller and more maintainable. Unfortunately, some of these fields (in this case, disk and network on google_compute_instance especially) are heavily used in other resources' tests, documentation, etc. Getting all the tests and documentation updated takes time.
  • Some of our breaking changes (the disk migration) are very complex and hard to test. We wanted to take ample time with these to try and make sure that upgrading was a smooth, error-free experience. Unfortunately, even with all our testing of these, we still experienced a migration error, necessitating 1.0.1 getting sent out just a few hours later. So even with all the time we took on this, we probably should have taken a little bit more.

Again, I regret the delay in getting this release out the door. We'll do our best to return to regularly-scheduled releases and smooth upgrade processes now. Thanks everyone, for your patience.

@AndreaGiardini
Copy link
Author

Thank you for the great work! :)

luis-silva pushed a commit to luis-silva/terraform-provider-google that referenced this issue May 21, 2019
@ghost
Copy link

ghost commented Mar 30, 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. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants