The user interface for restricted releases is a bit complex. Releases are restricted by license keys. The restricted releases also require an incrementing version number see issue #33.
The UI for this is a bit tricky. Ideally, a user can search for a license key directly, by customer, or by activation location ( website ). Each of these search options will return results formatted in a list, with each result displaying the license key, license status, and customer. If the user searches by activation location, the user will need visual confirmation of some kind.
When the result is selected, it will be appended to the list of whitelisted license keys. This will be saved via ajax.
The user interface for restricted releases is a bit complex. Releases are restricted by license keys. The restricted releases also require an incrementing version number see issue #33.
The UI for this is a bit tricky. Ideally, a user can search for a license key directly, by customer, or by activation location ( website ). Each of these search options will return results formatted in a list, with each result displaying the license key, license status, and customer. If the user searches by activation location, the user will need visual confirmation of some kind.
When the result is selected, it will be appended to the list of whitelisted license keys. This will be saved via ajax.