Cut RC1

[SteveLasker]

Proposing we release artifacts-spec-1.0.0-rc.1
Account for issues and PRs tagged RC1

High-level deliverables as follows:

• Decide on main commit for release - 9ff738f
• Cut branch named v1.0.0-rc.1 based on agreed upon main commit
• Cut a tag named v1.0.0-rc.1
• Update README.md

/cc @SteveLasker, @michaelb990, @justincormack, @sajayantony

Can the maintainers please respond with a +1 comment once you are in favor of cutting this release.

[SteveLasker]

awaiting #92 and #94 to be merged

[SteveLasker]

All active PRs are now merged, identified 9ff738f as the commit to cut RC.1

[michaelb990]

+1

[sajayantony]

+1 LGTM. @northtyphoon

[dlorenc]

Maybe a dumb question, but how is this spec intended to interact with the outcome from the OCI Reference Types Working Group? Is it intended to live side by side long-term, or will they merge?

[sajayantony]

@dlorenc  I think the ORAS project should evaluate the OCI Reference Type proposal once it has made it into Distribution, Image or Artifact Spec.

[sudo-bmitch]

That is disappointing. I had hoped that WG contributors would take a more active role in promoting the recommendations of the working group.

[michaelb990]

Hey @sudo-bmitch! Finalizing this RC is not intended to detract from the recommendations of the WG. Several of the maintainers of this project are active contributors and promoters of the WG, myself included. The WG discussions have informed this spec, and I intend to continue working on both. I don’t think it’s realistic for work outside the WG to halt, this is just a next step in work already in flight. If you want to talk more about this, feel free to ping me directly -- I’d like to keep this issue related to oras-project/artifacts-spec work.

[dlorenc]

If you want to talk more about this, feel free to ping me directly -- I’d like to keep this issue related to oras-project/artifacts-spec work.

Thanks @michaelb990 , I'll create a new issue with more questions on the future plans here.