-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate existing Test Pilot users to AMO #665
Comments
Oh, sure. Mostly just dropping the updateURL (it defaults to AMO). You can see the checklist I made for them at internetarchive/wayback-machine-firefox#84 |
@wresuolc I assume that we can't ever rename the extension can we? The id will always be that it is a test pilot experiment if so. |
It's a lot more complex to change the ID (basically involves you making a whole new add-on and publishing a new version of the old one that installs the new one). I'd leave the ID alone, personally. :) |
I was able to upload the 3.1.0 internally-signed 'Mozilla Extension' to AMO, so next week we should be able to upload the next and change the "How to distribute" to "On this site" |
@jonathanKingston - nevermind, looks like summary + description both come from the AMO admin interface. |
for #665: update title, desc, version for AMO
From https://discourse.mozilla.org/t/-/18918/3?u=grahamperrin (2017-08-07):
tl;dr if I understand correctly, you may find migrations occurring sooner than originally intended where users of Firefox Sync allow synchronisation of extensions. |
I dunno how this happens, I haven't been able to replicate it. My only assumption is the update servers were messed up for a while perhaps. |
Closing this happened. |
Congratulations on a successful Test Pilot run! We'd like to get this in AMO so you can start managing and pushing your updates. Below are the steps off the top of my head:
The text was updated successfully, but these errors were encountered: