You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I will add a v3 module with a patch version bump to comply with the go modules pattern. This will not break existing users, with or without go modules, because go module users will have to opt-in to using the new github.com/uber/h3-go/v3 import path.
plan for future development
all changes and improvements to v3.* will be made in the v3/ module, leaving the root module as-is. Users of the root module will need to move to the GOMODULE supported /v3 suffix import (github.com/uber/h3-go/v3) to pick up any changes/fixes introduced after v3.0.2.
rationale
future development will be made in the v3 module and not reflected in the root module in order to avoid copy/paste mistakes. Developing in the v3 module will also encourage adoption of the backwards compatible development practices encouraged by GOMODULES.
The text was updated successfully, but these errors were encountered:
This repo follows a modified version of semver, where the major version
of this repository tracks the major version of the C core repository.
This doesn't play well with GOMODULES by default, so we create our first
major version go module that is just a duplication of master version.
Solves #24
* add support for GOMODULES
This repo follows a modified version of semver, where the major version
of this repository tracks the major version of the C core repository.
This doesn't play well with GOMODULES by default, so we create our first
major version go module that is just a duplication of master version.
Solves #24
https://blog.golang.org/v2-go-modules
I will add a v3 module with a patch version bump to comply with the go modules pattern. This will not break existing users, with or without go modules, because go module users will have to opt-in to using the new
github.com/uber/h3-go/v3
import path.plan for future development
all changes and improvements to v3.* will be made in the
v3/
module, leaving the root module as-is. Users of the root module will need to move to the GOMODULE supported/v3
suffix import (github.com/uber/h3-go/v3
) to pick up any changes/fixes introduced after v3.0.2.rationale
future development will be made in the
v3
module and not reflected in the root module in order to avoid copy/paste mistakes. Developing in thev3
module will also encourage adoption of the backwards compatible development practices encouraged by GOMODULES.The text was updated successfully, but these errors were encountered: