-
Notifications
You must be signed in to change notification settings - Fork 61
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
Updated addon queue #56
Comments
+1 On this. Seems like reviews are all manual and nobody's getting around to doing them. Is there no automated, pre-review, score? |
Reviews are not entirely manual, only two questions are. Most addons should be reviewed within 2 days of publishing, re-reviews within a week, if not, please use the link on the addon page to 'Submit a correction', sometimes we miss an addon on accident. To answer the questions: |
visibility into the queue, or at least documentation of how it works would be helpful. All of our addons still appear as WIP b/c they were initially in private repos, but we've since open sourced most of them and had a few minor version releases. For example, see: https://emberobserver.com/addons/ember-arcgis-portal-services It shows last reviewed on August 26th 2017 for version 0.21.1 but we're currently on 0.29.0. I can't find any information on the site about when it will be reviewed next, but 6 months seems like a long time. One thing to note is that the way we open sourced this was to transfer ownership of the repository from one org to another - in other words the |
We got a really fast initial review of https://emberobserver.com/addons/ember-material-design-datepicker, but then none since. I imagine this is because there is a large backlog? A couple questions and suggestions about the 'queue'.
When we publish a second update, before you have reviewed the first update, do we maintain our place in the queue, or get put to the bottom again?
Could we get visibility of the queue in some way to see where addon reviews are?
The text was updated successfully, but these errors were encountered: