-
Notifications
You must be signed in to change notification settings - Fork 90
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
Docs for backwards compatibility #763
Conversation
35863b1
to
63bdef3
Compare
Would you be able to rebase or cherry-pick to remove the merge commits from the PR? I'd be happy to help out with that as well! |
63bdef3
to
d581da7
Compare
This PR is aimed at solving the issue no `closes nsidc#471`
d581da7
to
78d4cd6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work! I think we need a little more feedback from around the group, so I'll tag to discuss at a hack day! 🙇
Oh, right, let's get SPEC0 in there :) I think (but don't assume) we have a consensus that's what we want to do. Let's find out! :) |
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
Co-authored-by: Matt Fisher <[email protected]>
A couple minor TODOs left here @Sherwin-14, do you have time to take care of them, or would it be OK for a maintainer to finish this off? |
Yeah I just finished some important assignments so I can take care of this now but what changes do we need to accomodate? |
I think two TODOs left: adding a link to our API documentation ( No rush, and also we're happy to pick up the finishing touches if your schedule is too busy for now. Just let us know! |
I'll do both of them. But which section are we going to refer the SPEC0 policy, do we need to assign an entirely different section for this? |
I think a new section for SPEC0 makes sense. For example, "Our Python and dependency support policy" |
Co-authored-by: Matt Fisher <[email protected]>
Added the docs for backwards compatibility as per the issue descriptions. "resolves #471".
📚 Documentation preview 📚: https://earthaccess--763.org.readthedocs.build/en/763/