Track app versions

Bug #827490 reported by Anthony Lenton
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Developer registration portal
Fix Released
Michael Nelson

Bug 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.

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

Revision history for this message
Jonathan Lange (jml) wrote :

Note that even if the upload isn't a Debian source package, you might be able to guess the version from the tarball name or its top-level directory, e.g. foo-1.2.3.tar.gz or foo.tar.gz that unpacks to foo-1.2.3/.

Revision history for this message
Michael Nelson (michael.nelson) wrote :

Hrm, I'm struggling to find a place in the UI where it makes sense to ask/confirm the app version.

The first page when adding an app is where you upload your app, so it needs to be after this point if we want to extract it on the server*. But then it doesn't really belong or fit on any of the other pages (Finding your app, Showing your app, Licensing), and doesn't deserve an extra step.

* We could instead include the field on the first "Your app" page, after the upload field, and parse the version number from any file-name for upload on the client? So far, this would seem to make the most sense interaction wise? (ie. it's blank initially, but if you select a file for upload, any version will be matched from the filename and used to pre-populate the version field - if it's empty).

Revision history for this message
Anthony Lenton (elachuni) wrote :


Yep I completely agree. If we can't find a version name in the filename the version field can just be left blank for the developer to fill out manually, it's just a suggestion and not even a required field anyway.

description: updated
Changed in developer-portal:
assignee: nobody → Michael Nelson (michael.nelson)
status: New → Fix Committed
Changed in developer-portal:
milestone: none → 12.01
Changed in developer-portal:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers