Release 35.1.0

Aperta
#17,963 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, github, kotlin
Ambito
mobile, release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Kotlin
Stelle
5.7k
Fork
2.1k
Merge medio
1g 22h
PR unite (30g)
135

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/android

Tutte le issue di nextcloud/android

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.