# Review queue & distributing ways

**URL:** <https://forums.creativeclouddeveloper.com/t/review-queue-distributing-ways/2155>\
**Category:** UXP Plugin API\
**Created:** [November 2, 2020, 11:13am UTC](https://forums.creativeclouddeveloper.com/t/review-queue-distributing-ways/2155 "2020-11-02T11:13:21Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![kerrishotts](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/kerrishotts/32/8_2.png) [@kerrishotts](https://forums.creativeclouddeveloper.com/u/kerrishotts)\
**Post date:** [November 2, 2020, 6:04pm UTC](https://forums.creativeclouddeveloper.com/t/review-queue-distributing-ways/2155/3 "2020-11-02T18:04:09Z")

</div>

cc @ashryan for his feedback & comments.

To your points, @simonhenke:

- Going back to the end of the review queue is the only fair way to manage updates – otherwise the system could be gamed in ways that would slow down reviews for everyone else.
- Distribution via other channels using the same ID or different ID is up to you. If you use the _same ID_, then your user can opt-in to continue to receive updates from the marketplace when they are released. IMO, this is the smoothest option from the user’s perspective. If you use a different ID, the plugins act as two separate versions, and so a user with _both_ may end up confused as to which is which. Further, with a separate ID, there are no automatic update notifications.

I like @pklaschka’s take on doing this as an early-access/beta release process, where those who are OK w/ getting plugins via a website can still do so, while (assuming you use the same ID), getting the update notifications when approved & released on the marketplace.

---

_[View the full topic](https://forums.creativeclouddeveloper.com/t/review-queue-distributing-ways/2155)._
