| 2012-01-09 15:31:10 |
Michael Nelson |
description |
We should ask the developer to (optionally) provide a version for their submitted application as part of the initial submit workflow.
This information should be used as a packaging guideline only: If the uploaded tarball isn't an actual source package of some sort there isn't a version reported at all, and something needs to be used when putting together the package.
We shouldn't need to send out this version information as part of the available for-purchase apps API call, and we shouldn't need to enforce other checks (like providing an updated version number if the uploaded package is updated, or viceversa, or ensuring that the version field is always updated to some debian-greater version. |
We should ask the developer to (optionally) provide a version for their submitted application as part of the initial submit workflow.
This information should be used as a packaging guideline only: If the uploaded tarball isn't an actual source package of some sort there isn't a version reported at all, and something needs to be used when putting together the package.
We shouldn't need to send out this version information as part of the available for-purchase apps API call, and we shouldn't need to enforce other checks (like providing an updated version number if the uploaded package is updated, or viceversa, or ensuring that the version field is always updated to some debian-greater version.
QA Notes:
1) Create a new app as a developer,
2) On the first page you'll see an "App version number" field - leave it blank
3) Upload a tarball with a filename that includes a version number of some sort
4) The version field should have been pre-populated with the version number from the filename.
5) Enter any text in the version field and repeat (3)
6) The version field should not change |
|
