Release v1.0.0-rc.3

[duckontheweb]

Description:

Update version and CHANGELOG for v1.0.0-rc.3 release.

PR Checklist:

• Code is formatted (run pre-commit run --all-files)
• Tests pass (run scripts/test)
• Documentation has been updated to reflect changes, if applicable
• This PR maintains or improves overall codebase code coverage.
• Changes are added to the CHANGELOG. See the docs for information about adding to the changelog.

[codecov-commenter]

Codecov Report

Merging #532 (9ac2da6) into main (aa76c8d) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #532   +/-   ##
=======================================
  Coverage   94.25%   94.25%           
=======================================
  Files          71       71           
  Lines       10269    10269           
  Branches     1072     1072           
=======================================
  Hits         9679     9679           
  Misses        422      422           
  Partials      168      168           

Impacted Files	Coverage Δ
pystac/version.py	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aa76c8d...9ac2da6. Read the comment docs.

[l0b0]

Several of us at Toitū Te Whenua Land Information New Zealand are very keen for the 1.0 release. Are there any things in particular which you would like feedback on?

[duckontheweb]

Several of us at Toitū Te Whenua Land Information New Zealand are very keen for the 1.0 release. Are there any things in particular which you would like feedback on?

At this point we are really trying to make sure we get any potentially breaking changes in prior to a 1.0 release. As far as I can tell, the only remaining issues that fit that description are #481 (since it will change the API for working with CommonMetadata) and #315 (which will result in exceptions in cases that now return None). #380 also has the potential to break user code by changing the definition of equality, but I'm inclined to address that post-1.0 since I think it may take some time to flesh out and I'm not sure how many downstream applications are actually relying on a certain definition of equality.

I'm currently working on #481 and plan on tackling #315 after that unless someone else gets to it first and then I would anticipate putting out a 1.0 release after that.

@lossyrob Do you have any other thoughts on this?

[lossyrob]

I think we'd be ready for a full release after the changes you mentioned, and it will be great to fully unblock a lot of downstream work for STAC 1.0

There is also the work of updating the quickstart, tutorials, and any out-of-date documentation that's left to be done. Since we can render the v1.0 release docs off of the 1.0 release branch and not a tag, those doc updates could happen after the tag and pypi release are made.