Update extension publishing process#16592
Conversation
benja-M-1
requested review from
Bkblodget,
amyb12345,
felipecruz91,
gtardif and
lucbpz
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
amyb12345
left a comment
amyb12345
left a comment
There was a problem hiding this comment.
Have a few suggestions still before approving.
|
@amyb12345 : @felipecruz91 told me that he felt there should a clearer explanation of what the advantages of requesting a review are. And maybe make it more clear that there are two ways to submit and what to expect from each in their own section maybe. I am working on it now |
benja-M-1
force-pushed
the
extensions/self-publish-process
branch
from
f122d22 to
82ee3e8
Compare
| Extension team before listing your extension. Whether you choose one or the other, the publishing process will be | ||
| different. | ||
|
|
||
| #### No review requested |
There was a problem hiding this comment.
should we mention that a published not reviewed extension can request a review later?
aevesdocker
left a comment
aevesdocker
left a comment
There was a problem hiding this comment.
A few picky comments @benja-M-1, rest LGTM
benja-M-1
force-pushed
the
extensions/self-publish-process
branch
from
55bfe36 to
40745a9
Compare
|
@aevesdocker, what is the best way to proceed on this one? Should I turn it as ready for review and you'll know when to merge it as it is attached to a milestone? |
|
@benja-M-1 Yes, I'll take it from here! I won't miss anything attached to the milestone :) |
Introduce self-published and docker reviewd notions Apply suggestions from code review Co-authored-by: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Co-authored-by: Felipe Cruz Martinez <15997951+felipecruz91@users.noreply.github.com>
benja-M-1
force-pushed
the
extensions/self-publish-process
branch
from
7bddeef to
37ad672
Compare
|
I made some changes: I used the card component to make the two publish options more visible. |
4 participants
Do not merge before the 4.17 Docker Desktop release
Proposed changes
We are in the process of updating how extensions are published in the marketplace. This process will be live when Docker Desktop 4.17 will be released, later in February.
See the overview of the process here : https://deploy-preview-16592--docsdocker.netlify.app/desktop/extensions-sdk/process/
See the publish page here : https://deploy-preview-16592--docsdocker.netlify.app/desktop/extensions-sdk/extensions/publish/
In the meantime, this PR fixes the toc from where the validate page was missing.
Related issues (optional)