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

Define CAR v2 as a separate go module #79

Merged
merged 2 commits into from
Jun 10, 2021
Merged

Define CAR v2 as a separate go module #79

merged 2 commits into from
Jun 10, 2021

Conversation

masih
Copy link
Member

@masih masih commented Jun 10, 2021

Note, the entire approach to CAR v2 implementation and package structure is work in progress, hence this PR is against wip/v2. For context see #78 (comment)

Since we are releasing a new major version, define a new go module for
the CAR v2 implementation, following the recommendations here:

The module is versioned as go 1.15 to maintain compatibility as pointed
out by comment here:

Since we are releasing a new major version, define a new go module for
the CAR v2 implementation, following the recommendations here:
- https://blog.golang.org/v2-go-modules

The module is versioned as go 1.15 to maintain compatibility as pointed
out by comment here:
- #75 (comment)
@masih masih self-assigned this Jun 10, 2021
@masih masih requested review from mvdan, willscott and rvagg June 10, 2021 10:04
We might want to get this fixed at source; it is valid for a module to
have no go files i think, and CI should tolerate that.
@masih masih added the kind/enhancement A net-new feature or improvement to an existing feature label Jun 10, 2021
Copy link
Contributor

@magik6k magik6k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/v2 may not work too well with how Go handles v2/vX tags

Copy link
Contributor

@mvdan mvdan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prefix/v1.2.3 is recognized by Go, but I think this should be fine given it's not semver. you could always go for wip-v2 to be on the safer side.

@masih
Copy link
Member Author

masih commented Jun 10, 2021

Thank you both for the reviews. I'll go ahead with merge since all of this is under WIP anyway. once there is a functional mass we can then re-evaluate the module structure for the path of least resistance 🍻

@masih masih merged commit 0c1de83 into ipld:wip/v2 Jun 10, 2021
@masih masih deleted the define-go-mod branch June 10, 2021 10:46
@masih masih added this to the CAR v2 milestone Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A net-new feature or improvement to an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants