Replies: 3 comments 1 reply
-
All of the sub-proposal links to the proposal text are broken (404). Is this expected? Example:
|
Beta Was this translation helpful? Give feedback.
-
Based on the excellent feedback received from CUE users to date, and updates shared on the various modules update calls, the consensus appears to be that this proposal and its various sub proposals should be accepted. As discussed on the 2024-05-02 modules update call, we are therefore moving this proposal and its sub-proposals to a status of "likely accept". This marks the final period for comments that might change the recognition of consensus. We are aiming to conclude this decision at the next Modules Feedback session (2024/05/16). If there is no change in that consensus, we will accept the proposal and its sub-proposals on that date. |
Beta Was this translation helpful? Give feedback.
-
On the 2024-05-16 Modules update call we accepted v3 of the modules proposal and its sub-proposals. Closing this discussion to recognise that decision. |
Beta Was this translation helpful? Give feedback.
-
Modules and package management proposal v3
This discussion is for a proposal on how CUE can fully support package and dependency management.
It follows two earlier proposals:
Since V2, many people have provided their feedback and experimental code, now
part of the CUE repository, has been written that implements a form of the proposal.
This discussion presents a revised form of the proposal in the light of the above.
The revised proposal can be found here:
https://github.com/cue-lang/proposal/blob/main/designs/modules.v3/2939-modules.md
It incorporates the following sub-proposals:
To summarize the principal differences from V2 of the proposal:
pushing directly to a registry.
Some aspects of #2330 remain relevant but have not yet been implemented. Specifically:
provided by the OCI registry itself
Beta Was this translation helpful? Give feedback.
All reactions