wbrawner/thunderbird-android
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update REALEASING for new app location

Browse source
This commit is contained in:
Wolf-Martell Montwé 2024-01-17 15:01:18 +01:00
parent 28892810f4
commit 90fcb67209
No known key found for this signature in database
GPG key ID: 6D45B21512ACBF72
1 changed files with 37 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

48
docs/RELEASING.md
View file

@ -11,28 +11,50 @@
k9mail.keyPassword=<password 'k9mail@tb-android' in 1Password>
```
## One-time setup for F-Droid builds
### One-time setup for F-Droid builds
1. Install _fdroidserver_ by following the [installation instructions](https://f-droid.org/docs/Installing_the_Server_and_Repo_Tools).
2. [Sign up for a Gitlab account](https://gitlab.com/users/sign_up) and fork the [fdroiddata](https://gitlab.com/fdroid/fdroiddata) repository.
1. Install _fdroidserver_ by following
the [installation instructions](https://f-droid.org/docs/Installing_the_Server_and_Repo_Tools).
1. On MacOS, it's best to install the latest version from source, because the version in Homebrew has some issues.
1. Install the android command line tools if not available already.
```
brew install --cask android-commandlinetools
```
2. Install latest _fdroidserver_ from source:
```
python -m venv fdroidserver-env
source fdroidserver-env/bin/activate
pip install git+https://gitlab.com/fdroid/fdroidserver.git
```
3. To use _fdroidserver_ from the command line, you need to activate the virtual environment before each use:
```
source fdroidserver-env/bin/activate
```
4. To deactivate the virtual environment:
```
deactivate
```
2. [Sign up for a Gitlab account](https://gitlab.com/users/sign_up) and fork
the [fdroiddata](https://gitlab.com/fdroid/fdroiddata) repository.
3. Clone your fork of the _fdroiddata_ repository.
## Release a beta version
1. Update versionCode and versionName in `app/k9mail/build.gradle`
1. Update versionCode and versionName in `app-k9mail/build.gradle.kts`
2. Create change log entries in
- `app/ui/legacy/src/main/res/raw/changelog_master.xml`
- `fastlane/metadata/android/en-US/changelogs/${versionCode}.txt`
- `app-k9mail/fastlane/metadata/android/en-US/changelogs/${versionCode}.txt`
Use past tense. Try to keep them high level. Focus on the user (experience).
3. Commit the changes. Message: "Version $versionName"
4. Run `gradlew clean :app:k9mail:assembleRelease --no-build-cache`
4. Run `./gradlew clean :app-k9mail:assembleRelease --no-build-cache --no-configuration-cache`
5. Update an existing installation to make sure the app is signed with the proper key and runs on a real device.
```
adb install -r app/k9mail/build/outputs/apk/release/k9mail-release.apk
adb install -r app-k9mail/build/outputs/apk/release/app-k9mail-release.apk
```
6. Tag as $versionName, e.g. `6.508`
7. Copy `app/k9mail/build/outputs/apk/release/k9mail-release.apk` as `k9-${versionName}.apk` to Google Drive (MZLA Team > K9 > APKs)
8. Change versionName in `app/k9mail/build.gradle` to next version name followed by `-SNAPSHOT`
7. Copy `app-k9mail/build/outputs/apk/release/app-k9mail-release.apk` as `k9-${versionName}.apk` to Google Drive (MZLA
Team > K9 > APKs)
8. Change versionName in `app-k9mail/build.gradle.kts` to next version name followed by `-SNAPSHOT`
9. Commit the changes. Message: "Prepare for version $newVersionName"
10. Update `gh-pages` branch with the new change log
11. Push `main` branch
@ -57,11 +79,15 @@
1. Fetch the latest changes from the _fdroiddata_ repository.
2. Switch to a new branch in your copy of the _fdroiddata_ repository.
3. Edit `metadata/com.fsck.k9.yml` to create a new entry for the version you want to release. Usually it's copy & paste of the previous entry and adjusting `versionName`, `versionCode`, and `commit` (use the tag name). Leave `CurrentVersion` and `CurrentVersionCode` unchanged. Those specify which version is the stable/recommended build.
3. Edit `metadata/com.fsck.k9.yml` to create a new entry for the version you want to release. Usually it's copy & paste
of the previous entry and adjusting `versionName`, `versionCode`, and `commit` (use the tag name).
Leave `CurrentVersion` and `CurrentVersionCode` unchanged. Those specify which version is the stable/recommended
build.
4. Commit the changes. Message: "Update K-9 Mail to $newVersionName"
5. Run `fdroid build --latest com.fsck.k9` to build the project using F-Droid's toolchain.
6. Push the changes to your fork of the _fdroiddata_ repository.
7. Open a merge request on Gitlab. (The message from the server after the push in the previous step should contain a URL)
7. Open a merge request on Gitlab. (The message from the server after the push in the previous step should contain a
URL)
8. Select the _App update_ template and fill it out.
9. Create merge request and the F-Droid team will do the rest.