Docs for backwards compatibility

[Sherwin-14]

Added the docs for backwards compatibility as per the issue descriptions. "resolves #471".

---

📚 Documentation preview 📚: https://earthaccess--763.org.readthedocs.build/en/763/

[mfisher87]

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!

[mfisher87]

Awesome work! I think we need a little more feedback from around the group, so I'll tag to discuss at a hack day! 🙇

[mfisher87]

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! :)

[mfisher87]

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?

[Sherwin-14]

Yeah I just finished some important assignments so I can take care of this now but what changes do we need to accomodate?

[mfisher87]

I think two TODOs left: adding a link to our API documentation (user-reference/api/api); and adding a reference to SPEC0 as our dependency deprecation policy.

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!

[Sherwin-14]

I think two TODOs left: adding a link to our API documentation (user-reference/api/api); and adding a reference to SPEC0 as our dependency deprecation policy.

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?

[mfisher87]

I think a new section for SPEC0 makes sense. For example, "Our Python and dependency support policy"

[Sherwin-14]

Apologies, I'm just now noticing that there's no navigation link to this page yet (https://earthaccess--763.org.readthedocs.build/en/763/)!

Can you update mkdocs.yml accordingly? Don't forget to double check the preview :)

Have we decided the channel where we would announce our releases?

[mfisher87]

For now, let's just use GitHub Releases as our only announcement channel. We may later have a newsletter or blog that we'll use, but for now we don't have those things. The #earthaccess channel in the Openscapes is semi-private (you have to ask to join, but we're just approving everyone who asks), so I don't think it should be listed.

This is looking really good, and I'm excited to merge! Can you @ me or re-request a review from me as soon as you have that final touch applied?

[mfisher87]

Amazing work, thank you!