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

Add reminder to upgrade to 1.0.0 #132

Closed
jbants opened this issue Apr 23, 2021 · 9 comments
Closed

Add reminder to upgrade to 1.0.0 #132

jbants opened this issue Apr 23, 2021 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@jbants
Copy link
Collaborator

jbants commented Apr 23, 2021

Add a friendly reminder to upgrade to stac version 1.0.0 for older stac versions.

@jonhealy1 jonhealy1 self-assigned this Apr 29, 2021
@jonhealy1
Copy link
Collaborator

@jbants Should this wait for the 1.0.0 release or should we ask people to upgrade to 1.0.0-rc.2?

@jbants
Copy link
Collaborator Author

jbants commented May 1, 2021

Let's wait for the STAC 1.0.0 release.

@jbants jbants added v2.2.0 and removed v.2.1.0 labels May 6, 2021
@jbants
Copy link
Collaborator Author

jbants commented May 18, 2021

relates to #115

@jbants jbants added enhancement New feature or request and removed v2.2.0 labels May 24, 2021
@jbants jbants added this to the 2.3.0 milestone May 24, 2021
@gadomski
Copy link
Member

@jbants this milestone should probably be removed/changed, yes?

@jonhealy1
Copy link
Collaborator

I did add this reminder to stac-check but it's not in stac-validator yet

@gadomski
Copy link
Member

Yeah, but the milestone for this issue is 2.3.0, and we're already on 3.0.0?

@jonhealy1
Copy link
Collaborator

Haha true

@jonhealy1 jonhealy1 removed this from the 2.3.0 milestone Apr 22, 2022
@jonhealy1
Copy link
Collaborator

Should I make this a milestone to 3.1.0? I don't think it's needed - it's more of a thing for stac-check which gives hints and warnings and not just pure validation

@gadomski
Copy link
Member

Yeah, this would just be a feature addition so it could go into a v3.1.0. However, I haven't looked to see whether there's been any breaking changes since v3.0.0 that would require a major version bump, we should check that before we decide what the next milestone is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants