Skip to content

Implement Info in the oci store content implementation#187

Merged
shizhMSFT merged 1 commit into
oras-project:v1from
oanatmaria:aserto/implement_info
Jun 21, 2022
Merged

Implement Info in the oci store content implementation#187
shizhMSFT merged 1 commit into
oras-project:v1from
oanatmaria:aserto/implement_info

Conversation

@oanatmaria
Copy link
Copy Markdown
Contributor

@oanatmaria oanatmaria commented Jun 20, 2022

Signed-off-by: oanatmaria oana@aserto.com

@oanatmaria oanatmaria force-pushed the aserto/implement_info branch from 41c496a to bb3093b Compare June 20, 2022 10:29
Signed-off-by: oanatmaria <oana@aserto.com>
@oanatmaria oanatmaria force-pushed the aserto/implement_info branch from bb3093b to 96dcb2d Compare June 20, 2022 10:39
@viovanov
Copy link
Copy Markdown
Contributor

Hi @shizhMSFT !
One more please? :)

Copy link
Copy Markdown
Contributor

@shizhMSFT shizhMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@shizhMSFT shizhMSFT merged commit a5cf23a into oras-project:v1 Jun 21, 2022
@FeynmanZhou
Copy link
Copy Markdown
Member

FeynmanZhou commented Aug 23, 2022

Hi @viovanov ,

I think we can prepare a new release for v1 to include this change. Considering ORAS-go v2 is still experimental, ORAS-go v1 will be maintained by the ORAS community until ORAS v2 GA. Currently, ORAS-go v1 is not under active development, thus the ORAS community will only publish new releases to include necessary fixes/updates at a low rate.

As ORAS-go v1 was released quarterly and the latest release was Jun 15, do you accept planning the next release of v1 in the mid of Sep?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants