Pierre Prinetti
Pierre Prinetti
Following comments by @mandre, we might want to be able to issue backports. Turns out, the same-branch strategy lets us do that while still keeping the active version on the...
> Do these really have to be breaking changes tho? Indeed, you are right: all changes that can be non-breaking should be non-breaking. I'll put aside my purist self and...
This is your last chance to let me know it's a bad idea! I am soon going to tag [the current tip](https://github.com/gophercloud/gophercloud/commit/0721d75e876f20e0f3f9be83b3133fa3476ee992) as `v1.0.0`. Existing clients importing `github.com/gophercloud/gophercloud` will automatically...
https://github.com/gophercloud/gophercloud/releases/tag/v1.0.0
Labeling as semver:major as the current implementation introduces a breaking change.
Type change is a breaking change. cf.: https://go.dev/play/p/b4su08crVCn
> Introducing a number of new functions with the WithContext suffix is too much I would like to be able to accept a per-call `context.Context`. One backwards-compatible (and low-effort) implementation...
We had our first **and last** internal Red Hat meeting about Gophercloud. As detailed down below, **further discussions will be public and publicly advertised**. Attendees: @pierreprinetti @mdbooth @EmilienM @mandre @ericarrakis...