Release 35.1.0

Abierto
#17,963 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, github, kotlin
Área
mobile, release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
Kotlin
Estrellas
5.7k
Forks
2.1k
Merge medio
1 d 22 h
PR fusionados (30 d)
135

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nextcloud/android

Todos los issues de nextcloud/android

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.