nextcloud / nextcloud/talk-android

Release x.y.z - Roadmap

Open
#1,346 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

overview
Dominant language
Kotlin
Stars
739
Forks
321
Avg merge
14h 59m
Merged PRs (30d)
151

Description

Planned RC1: ~2+ weeks before a stable and 6 week after latest feature/mayor release / replace with date

Release/EOL Management preparations (do this when creating new roadmap)

  • Create milestone
  • Check if oldest Android version is EOL by Google and user usage <= 0.5% and drop it if so for all apps (talk, files, notes)
    • Search for usage of Build.VERSION_CODES.xy
    • Announce it in changelog

Create stable-x.y branch & use it for release (when releasing RC1)

  • Create branch stable-x.y
  • Update stableBranchin scripts/analysis/analysis-wrapper.sh to stable-x.y on stable branch
  • Check that transifex bot still works
  • Enable branch to be analyzed on codacy
  • Update versionCode in app/build.gradle on master to next minor version

Test app with all supported Android versions

  • Access all activities/controllers
  • Chat: previews (media/contacts), text/voice-messages, reply/swipe-reply, delete, share file
  • Call: audio/video
  • Switch accounts
  • Dark/light theme

All tests on

  • Android 5
  • Android 6
  • Android 7
  • Android 8
  • Android 9
  • Android 10
  • Android 11
  • Android 12
  • Android 13

RC1

  • Inform marketing about changelog and expected release date

Final Release, after two weeks time (max) of latest RC release

  • Bump versionCode in app/build.gradle file
  • Verify that the new version number is shown in settings
  • Tag version as "vx.y.z" (as in ^v[0-9]+\.[0-9]+\.[0-9]+$)
  • Verify that it is shown on F-Droid (within 24h)
  • In case there were security issues fixed ping the security team

After release

  • x.y - 1
    • Delete stable-x.y-1 branch
  • x.y
    • Create milestone vx.y.1
    • Schedule x.y.1 RC1 3 weeks after stable, release ~4 weeks
    • Create overview issue
  • x.y + 1
    • Create milestone x.y+1
    • Create overview issue & adjust date, handle bumps

Backports:

Open PRs:

Marketing:
@jospoortvliet

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use this checklist as the release plan, starting with the milestone and stable-x.y branch steps. Read scripts/analysis/analysis-wrapper.sh and app/build.gradle, then review the supported Android-version test matrix and RC1/final-release checks. Done means the release branch, version metadata, testing, tags, and post-release milestones are all handled.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.