(MAJOR) Prepare for stable API (1.0) release #151
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I believe that this crate is ready for API stabilization.
I'm seeking discussion regarding committing to the existing API as a stable interface over the next month. Barring unresolved feedback, this PR will be merged on 5 December 2022 and a 1.0 release issued at that time.
Between now and then, I welcome feedback on any issues or concerns that should block or delay a 1.0 release. Please review this crate and remaining APIs from the underlying C++ XMP Toolkit with an eye toward what might cause breaking API changes.
I believe the following are not in scope for 1.0 release:
XMP_Meta
,XMP_Files
, andTXMPUtils
. (There are relatively few left and these may be added in 1.x releases.)I___
API surface).Please either file issues here in GitHub or add comments to this PR while discussion is open.