ORAS v1.2.0 milestone discussion #1119
FeynmanZhou
started this conversation in
General
Replies: 4 comments 6 replies
-
We agreed to move #816 to milestone v1.2.0 based on the community meeting discussion on Sep 13, 2023. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi! Is there an estimated time period for releasing 1.2.0? |
Beta Was this translation helpful? Give feedback.
4 replies
-
Hi @FeynmanZhou, what is the expected timeline for the release of 1.2.0? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
ORAS is following a quarter-based release cadence in 2023. ORAS v1.1.0 was released on Sep 5. It's time to determine the v1.2.0 release plan and kick off the work for v1.2.0 in the community. After triaging all issues, I grouped the major enhancements into five aspects as follows. Some enhancements are suggested as critical and some are nice to have.
Based on the quarterly release cycle, the release date could be set to the middle of December.
This is an open discussion and I am also open to any suggestions. Feel free to share anything feature requests you think are missing below or should be prioritized.
Major enhancements
Standardize the CLI output for scripting experience and improve output experience
Provide a progress bar to improve the usability of content transportation. Standardize the CLI output for scripting experience.
Improve verbose logs for all ORAS commands to enhance the troubleshooting experience
Make the verbose logs consistent, useful, concise, and human-readable. Users can easily locate the root cause by analyzing the verbose logs. Formulize the CLI output guideline to provide a unified reference for future command output.
This issue #1053 relies on oras-project/oras-go#576
Simplify image lifecycle metadata management experience through annotations
Users can easily update the image lifecycle metadata without learning the OCI Spec. Annotating experience is critical to users who want to attach or add image lifecycle metadata. The annotating functionality is useful for software supply chain scenarios such as adding "End-of-support" metadata to an OCI image.
Optimize ORAS performance
Decrease the auth request time to optimize ORAS performance.
oras cp
#1105This issue relies on oras-project/oras-go#594
Support multi-arch image index management (Nice to have)
Most of the open-source projects support multi-arch images. Enable users to push/attach a multi-arch image or an image index by leveraging the OCI image index.
--platform
inoras push
andoras attach
#1066Complement OCI layout management (Nice to have)
ORAS has a few deletion capabilities for some ORAS commands that are not supported in the OCI image layout. Complement OCI layout management enables users to better manage the OCI image layout.
oras blob delete
#761oras manifest delete
#762These two issues rely on oras-project/oras-go#454
Automate installation package manager (Winget, Snap) management (Nice to have)
Beta Was this translation helpful? Give feedback.
All reactions