tag | a1c482f64e921b5adcfdbe5a0fd7f127e66e549f | |
---|---|---|
tagger | avm99963 <me@avm99963.com> | Wed Sep 09 01:30:07 2020 +0200 |
object | adca259b47de608c9c7ff2556a5fb412b49bd767 |
v1.4.1 Changelog: https://gerrit.avm99963.com/plugins/gitiles/infinitegforums/+log/refs/tags/v1.4..refs/tags/v1.4.1
commit | adca259b47de608c9c7ff2556a5fb412b49bd767 | [log] [tgz] |
---|---|---|
author | avm99963 <me@avm99963.com> | Wed Sep 09 01:18:49 2020 +0200 |
committer | avm99963 <me@avm99963.com> | Wed Sep 09 01:18:49 2020 +0200 |
tree | 38eb15dcc814fab65ed05db6fdc476fd8e186a00 | |
parent | 95da0774d8118051636d788decedfc8f2f4ef645 [diff] |
Improve post count documentation Make clear that the post count only takes into account posts made in the current forum and doesn't actually count all posts across all forums. Change-Id: Ia59e16700556d8ede8bf46d514c42dc6d90776b0
An extension which brings several enhancements to the Google Forums and the Community Console.
When the code in the master
branch is considered to be stable, a release can be made. This is the procedure:
vx
, where x is the extension's version number for that release) by running bash tagRelease.bash --version vx
. Note that the tag must be pushed to Gerrit after being created.Afterwards, the release/build files must be submitted to the Chrome Web Store and addons.mozilla.org.
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.
The procedure is similar to the one with the Chrome Web Store.
@TODO: Add more details once the first version of the extension has been uploaded to addons.mozilla.org.
A zip file with the contents of the extension, which can be uploaded to the Chrome Web Store and addons.mozilla.org, can be created with any of the following procedures:
Run bash release.bash -h
in order to learn how to use this command. To summarize, the command accepts the --channel
and --browser
flags (or their short versions -c
and -b
).
As an example, if you wanted to create a ZIP file of the beta-branded extension targeted for Firefox, you would run bash release.bash -c beta -b gecko
.
You can also use make to build the extension. This is just a wrapper for the release.bash
command.
Run make all
to build the extension for all the available channels and browsers. You can also run make {target}
where {target}
is one of the following: chromium-stable
, chromium-beta
, gecko-stable
, gecko-beta
.
Run make clean
to clean all the release files (this removes the out
folder, which is where the release files are saved).
When testing the extension during development, you don't have to build the extension each time you want to import an updated version to Chrome/Firefox. Instead, run bash generateManifest.bash {browser}
once, where {browser}
is either CHROMIUM
or GECKO
, and this will generate a manifest.json
file for the specified browser in the src
directory. Now, you can load the src
folder directly in the browser in order to import the extension, which removes the need to build it. When the manifest.gjson
file is modified, you'll have to generate the manifest again.
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.
The beta channel for Chrome is available here.