Gitiles
Code Review Sign In
gerrit.avm99963.com / infinitegforums / 666575fb534e9a4762a5a9c76adfd142dbca1771
commit666575fb534e9a4762a5a9c76adfd142dbca1771[log] [tgz]
authoravm99963 <me@avm99963.com>Sat Aug 08 15:40:39 2020 +0200
committeravm99963 <me@avm99963.com>Sat Aug 08 15:51:58 2020 +0200
tree0cf012050c3ab274ed743db306d775bf97866e8e
parent53057074774e1e1dc1b58398b8d66f3015044ce8 [diff]
Change the release system to a tag-based system

Before, releases were created by commiting a change to the manifest.json
file which updated the "version" field.

This commit changes this procedure by generating the version strings
directly in the release.bash script with the "git describe" command,
based on annotated Git tags.

Change-Id: I4de4e1040b7e9d22b4d3c8df9c0870989d966c49
3 files changed
tree: 0cf012050c3ab274ed743db306d775bf97866e8e
  1. .github/
  2. src/
  3. .gitignore
  4. README.md
  5. release.bash
README.md

Infinite scroll in TW

Available in the Chrome Web Store

Release cycle

When the code in the master branch is considered to be stable, a release can be made. This is the procedure:

  1. Tag the last commit with a version number (in the format vx, where x is the extension's version number for that release) by running git tag -a vx -m "vx". Note that the tag should be an annotated tag and not a lightweight tag, and it must be pushed to Gerrit after being created.
  2. Build the extension for both the stable and beta channels (this is explained in the next section). This will output a ZIP file for each release channel.
  3. Upload both release files to the Chrome Web Store, one for each release channel.
  4. Submit both releases to be reviewed by the Chrome Web Store team, but in the case of the stable channel uncheck the "Publish automatically after it has passed review" option.
  5. Upload the beta release file to the GitHub releases page under the newly created tag. Mark that release as a pre-release at GitHub.
  6. Wait until the beta release is reviewed and approved by Google.
  7. Test again the extension by using the beta channel. Check if the options have been transfered correctly from version to version, and wait some days (for instance between 3 and 5 days) to see if other people report issues with the updated version.
  8. If everything goes well, publish the update in the stable channel. The updated version should have already been reviewed by the Chrome Web Store team at this time.
  9. Update the release file in the GitHub releases page by removing the beta release file and uploading the stable release file. Also, remove the pre-release label.

If during this process the release wasn't approved by Google or an issue was found during beta testing, a new release which fixes this should be created.

Build the extension

To create a zip file with the contents of the extension, which can be uploaded to the Chrome Web Store, run bash release.bash. You can also use bash release.bash --channel=beta to include a beta label in the extension name and version of the resulting zip file.

The ZIP file will contain a manifest.json file with the according version name, and will be located in the out folder.

You can also get information about how to use the release.bash script by running bash release.bash -h.

Testing notes

To test translations, you might want to set your browser's locale. This section tells you how to set the locale in Windows, Mac OS X, Linux, and Chrome OS.

Beta channel

The beta channel is available here.