[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] 02/02: Add paragraph about how to release Android apps
From: |
gnunet |
Subject: |
[taler-docs] 02/02: Add paragraph about how to release Android apps |
Date: |
Thu, 04 Feb 2021 16:27:40 +0100 |
This is an automated email from the git hooks/post-receive script.
torsten-grote pushed a commit to branch master
in repository docs.
commit 26ecf8cee12510673a6e26398e9e8e3c40c7c897
Author: Torsten Grote <t@grobox.de>
AuthorDate: Thu Feb 4 12:26:06 2021 -0300
Add paragraph about how to release Android apps
---
taler-developer-manual.rst | 45 +++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst
index 8655ae4..a114847 100644
--- a/taler-developer-manual.rst
+++ b/taler-developer-manual.rst
@@ -903,6 +903,51 @@ Then you can merge in translations commit from the weblate
remote:
Afterwards, build the entire project from source and test the UI
to ensure that no erroneous translations (missing placeholders) are breaking
things.
+Release process
+---------------
+
+After extensive testing, the code making up a new release should get a signed
git tag.
+The current tag format is:
+
+* cashier-$VERSION
+* pos-$VERSION
+* wallet-$VERSION (where $VERSION has a v prefix)
+
+.. code-block:: console
+
+ $ git tag -s $APP-$VERSION
+
+F-Droid
+^^^^^^^
+Nightly builds get published automatically (see above) after pushing code to
the official repo.
+Actual releases get picked up by F-Droid's official repository via git tags.
+So ensure that all releases get tagged properly.
+
+Some information for F-Droid official repository debugging:
+
+* Wallet: [`metadata
<https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/net.taler.wallet.fdroid.yml>`__]
[`build log
<https://f-droid.org/wiki/page/net.taler.wallet.fdroid/lastbuild>`__]
+* Cashier: [`metadata
<https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/net.taler.cashier.yml>`__]
[`build log <https://f-droid.org/wiki/page/net.taler.cashier/lastbuild>`__]
+* PoS: [`metadata
<https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/net.taler.merchantpos.yml>`__]
[`build log <https://f-droid.org/wiki/page/net.taler.merchantpos/lastbuild>`__]
+
+Google Play
+^^^^^^^^^^^
+Google Play uploads are managed via `Fastlane
<https://docs.fastlane.tools/getting-started/android/setup/>`__.
+Before proceeding, ensure that this is properly set up
+and that you have access to the Google Play API.
+
+To release an app, enter into its respective folder and run fastlane:
+
+.. code-block:: console
+
+ $ bundle exec fastlane
+
+Then select the deploy option.
+Note this requires access to the Google Play upload signing key
+set via the various environment variables in $app/fastlane/Fastfile.
+
+All uploads are going to the beta track by default.
+These can be promoted to production later or immediately after upload if you
feel daring.
+
.. _Code-coverage:
Code Coverage
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.