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

Some IPFS repos incorrectly use v1 #8832

Open
3 of 6 tasks
guseggert opened this issue Mar 30, 2022 · 0 comments
Open
3 of 6 tasks

Some IPFS repos incorrectly use v1 #8832

guseggert opened this issue Mar 30, 2022 · 0 comments
Labels
kind/enhancement A net-new feature or improvement to an existing feature

Comments

@guseggert
Copy link
Contributor

Checklist

  • My issue is specific & actionable.
  • I am not suggesting a protocol enhancement.
  • I have searched on the issue tracker for my issue.

Description

Some IPFS repos such as https://github.com/ipfs/go-ipfs-blockstore have released a v1, but we actually don't intend to follow idiomatic semver on those, because we intent to release breaking minor version releases to avoid a v2 bump and then the subsequent import path change. This indicates that they are not really v1, but a v0 fork.

So we need to:

  • Identify all the repos incorrectly released as v1
  • Add a warning at the top of each repo's README describing that it doesn't follow standard semver (minor version v1 releases can still be breaking)
  • Prioritize them for consolidation as part of Consolidate IPFS Repositories #8543
@guseggert guseggert added the kind/enhancement A net-new feature or improvement to an existing feature label Mar 30, 2022
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

No branches or pull requests

1 participant