-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New version update submission flow for Listed and Unlisted #3481
New version update submission flow for Listed and Unlisted #3481
Comments
Three parts to the QA here:
|
Mixed Unlisted & Listed VersionsOptional QA for the 2016-11-17 push but it would be good to know sooner rather than later if the flow is broken at least. Don't try this on prod as the rest of the site can't handle mixed unlisted and listed versions on the same add-on yet. You will need to enable waffle switch The key differences are the upload flow contains a link under the channel description to change it (goes back to a distribution step). If you upload an unlisted version on a listed add-on not a great deal different happens during the flow; if you upload a listed version on an unlisted add-on then the details step should appear like you see during new add-on submission to collect missing metadata. Right now there isn't a way to identify the different channels of the versions anywhere, but #3482 will add this. |
@eviljeff : at point 2, in your comment, you wanted to say unlisted version on unlisted add-on , yes? Thanks! |
@ValentinaPC yes, I did. corrected. |
This can be marked as verified fixed, because all above bugs were fixed and verified. |
Part of #3477
The add-on version update submission flow will have a look and feel more consistent with the new add-on submission flow. Also, at this point it will be possible to choose a different channel for new versions, which means
channel
will no longer be set based onis_listed
. UX for this new flow is in #192.The text was updated successfully, but these errors were encountered: