Skip to content
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

Closed
5 of 8 tasks
groovecoder opened this issue Jul 11, 2017 · 8 comments
Closed
5 of 8 tasks

Migrate existing Test Pilot users to AMO #665

groovecoder opened this issue Jul 11, 2017 · 8 comments
Assignees
Milestone

Comments

@groovecoder
Copy link
Member

groovecoder commented Jul 11, 2017

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:

@groovecoder groovecoder added this to the AMO Launch milestone Jul 11, 2017
@ghost
Copy link

ghost commented Jul 11, 2017

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

@jonathanKingston
Copy link
Contributor

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

@ghost
Copy link

ghost commented Jul 11, 2017

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. :)

@groovecoder groovecoder self-assigned this Aug 22, 2017
@groovecoder
Copy link
Member Author

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"

@groovecoder
Copy link
Member Author

@jonathanKingston - nevermind, looks like summary + description both come from the AMO admin interface.

jonathanKingston added a commit that referenced this issue Aug 24, 2017
for #665: update title, desc, version for AMO
@grahamperrin
Copy link

From https://discourse.mozilla.org/t/-/18918/3?u=grahamperrin (2017-08-07):

… automation was probably with Firefox Sync. …

tl;dr if I understand correctly, you may find migrations occurring sooner than originally intended where users of Firefox Sync allow synchronisation of extensions.

@jonathanKingston
Copy link
Contributor

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.

@jonathanKingston
Copy link
Contributor

Closing this happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants