Release 35.1.0

Offen
#17,963 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
20/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
android, github, kotlin
Bereich
mobile, release

Rechercherichtung

This issue tracks the 35.1.0 release across the app, library, store listings, and supported Android versions. Start by reviewing the unchecked RC1 and final release checklist items, including build.gradle and /fastlane/metadata/android/en-US/changelogs/; then confirm the release steps with the maintainers. It is done when the release checklist is completed and the final release is verified on Google Play and F-Droid.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

overview

Planned RC1: 04.11.2026
Planned Release date:

Bump (do this when creating new roadmap)

  • create milestone
  • check if stable server version in drone.yml needs to be updated
  • bump version in MainApp
  • App
    • check if code is outdated due to last supported server version @NextcloudServer annotation
    • remove support for server older MINIMUM_SUPPORTED_SERVER_VERSION
  • Library
    • check if code is outdated due to last supported server version @NextcloudServer annotation
    • remove support for server older MINIMUM_SUPPORTED_SERVER_VERSION
  • check if oldest Android version is EOL by Google and user usage <= 0.5% and drop it if so
    • search for usage of Build.VERSION_CODES.xy
    • announce it in changelog
  • check if arm-v7a is still used in Google Play Console

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

  • create branch stable-x.y
    • enable branch to be analyzed on codacy
  • change on App
    • getBranchName.sh
    • analysis-wrapper.sh
    • detectWrongSettings.sh
    • check that transifex bot still works
  • change on Lib
    • create branch stable-2.x
    • enable branch to be analyzed on codacy
    • getBranchName.sh
    • analysis-wrapper.sh
  • Update version on master to next minor version

Test app with all supported Android version

  • access all activities
  • auto upload
  • upload / download files/folders
  • use external sdcard
  • what's new slides correctly shown on first start

All tests on

  • Android 8.1
  • Android 9
  • Android 11
  • Android 14
  • Android 15

RC1

  • Bump version code in build.gradle file
  • add what's new slides
  • replace screenshots (https://github.com/nextcloud/screenshots/tree/master/android/phone)
  • release new library version with rc-2.x.y-01 tag & use this is in app
  • release new SSO if needed
  • Verify that the new version number is shown in settings
  • Verify that logging is enabled
  • add $version.txt to /fastlane/metadata/android/en-US/changelogs/ to support GPlay version info
  • release with fastlane: creates GH release, uploads to Gplay, creates Gitlab MR for F-Droid
  • Verify that it is shown on F-Droid (within 24h)
  • inform marketing about changelog and expected release date

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

  • Bump version code in build.gradle file
  • set library to final tag
  • Verify that the new version number is shown in settings
  • Verify that logging is disabled
  • Test that what's new is shown correctly on upgrade
  • add $version.txt to /fastlane/metadata/android/en-US/changelogs/ to support GPlay version info
  • release with fastlane: creates GH release, uploads to Gplay, creates Gitlab MR for F-Droid
  • Verify that it is shown on F-Droid (within 24h)

After release

  • x.y-1
    • delete stable-x.y-1 branch
  • x.y
    • create milestone x.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

Vorherrschende Sprache
Kotlin
Sterne
5.7k
Forks
2.1k
Ø Merge
1 T. 22 Std.
Gemergte PRs (30 T.)
135

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nextcloud/android

Alle Issues in nextcloud/android

Ähnliche Issues

Weitere Issues zu Kotlin

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.