Uploading a new dev/beta/rc version of the add-on is restricted because of bad handling of the final optional number

RESOLVED WONTFIX

Status

--
major
RESOLVED WONTFIX
7 years ago
3 years ago

People

(Reporter: whimboo, Unassigned)

Tracking

Details

For some of my extensions I want to upload a dev version to AMO to let people immediately use new features. Therefore I have checked the following page how to do so: https://addons.mozilla.org/en-US/developers/docs/policies/maintenance#beta-addons

As given the naming of the XPI should be: "(a|alpha|b|beta|pre|rc)\d*$"

I tried a couple of ways but without luck. All the time the final number is getting removed after the upload, so another upload for the next version will fail with the error that the version of the extension is already present.

First upload:  memchaser-0.3pre1 -> 0.3pre
Second upload: memchaser-0.3pre2 -> 0.3pre (fail)

Right now I have to delete the formerly updated version of the extension and re-upload the new one. Not sure how this affects users of the formerly installed extension. I have tried and I don't get updates offered which is kinda bad. :(

Can we please fix this so we keep the optional number in the version string on AMO? Would there even be the chance to enhance it, so that I can upload a nightly version like: memchaser-0.3pre-201203230751.xpi?
Thanks for filing this.  Due to resource constraints we are closing bugs which we won't realistically be able to fix.  If you have a patch that applies to this bug please reopen.

For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.