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

Change the build process for v2.6 #600

Closed
ameshkov opened this Issue Mar 22, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@ameshkov
Member

ameshkov commented Mar 22, 2017

Build configurations

We should provide 3 different build configurations (just like we do now).

1. Dev

chrome
edge
opera
firefox-amo
firefox-standalone
firefox-legacy
safari

2. Beta

chrome-beta.zip
edge-beta
opera-beta
firefox-amo-beta
firefox-legacy-beta
firefox-standalone-beta
safari-beta

3. Release

chrome-release.zip
edge-release
opera-release
firefox-amo-beta-release
firefox-amo-release
firefox-legacy-release
firefox-standalone-release
safari-release

Self-hosted extensions

  1. Do not use chrome.adtidy.org for hosting extensions anymore.

  2. Use Github Pages branch to serve updates manifest files for self-hosted extensions.

    Which extensions are self-hosted:
    firefox-legacy-beta
    firefox-standalone-beta
    safari-beta

  3. Build output should contain update.rdf, update.xml and such.

@ameshkov ameshkov added this to the 2.6 milestone Mar 22, 2017

atropnikov added a commit that referenced this issue Mar 23, 2017

atropnikov added a commit that referenced this issue Mar 23, 2017

atropnikov added a commit that referenced this issue Mar 24, 2017

atropnikov added a commit that referenced this issue Mar 29, 2017

#600
Fix crx pack

atropnikov added a commit that referenced this issue Mar 30, 2017

#600
Fix Safari extension packing

atropnikov added a commit that referenced this issue Mar 30, 2017

@atropnikov atropnikov closed this Mar 30, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment