You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
communityCollaborate with and develop consensus with the Postgres communitydesignDesigning the architecture, protocols, tools, and interfaces for PGXN v2packaging
Determine the URI format for the OCI registry. Things to consider:
Will it be used for non-PGXN/Trunk images?
Where should extensions built from the core live?
Should we prefix PGXN-built extensions with pgxn to distinguish from other sources?
Should we expect to allow PGXN users to publish their own eventually?
What does the UX look like for users of the CLI?
How does it impact living all available packages?
Is it possible to make an API call to list all PGXN and core-provided extensions?
Or should core-provided extensions built by the PGXN build process use the same prefix as other PGXN distributions, even though core extension sources are not published on PGXN?
Done when a draft has been written up, submigged as an RFC pull request, and reviewed by members of the community.
The text was updated successfully, but these errors were encountered:
theory
added
design
Designing the architecture, protocols, tools, and interfaces for PGXN v2
packaging
community
Collaborate with and develop consensus with the Postgres community
labels
Sep 4, 2024
communityCollaborate with and develop consensus with the Postgres communitydesignDesigning the architecture, protocols, tools, and interfaces for PGXN v2packaging
Determine the URI format for the OCI registry. Things to consider:
pgxn
to distinguish from other sources?Done when a draft has been written up, submigged as an RFC pull request, and reviewed by members of the community.
The text was updated successfully, but these errors were encountered: