Release 35.1.0
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
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
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
-
OUTDATED_SERVER_VERSIONaccording https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule (e.g. NC12) - change if needed https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html#mobile-apps
- add these versions to changelog
-
- App
- check if code is outdated due to last supported server version
@NextcloudServerannotation - remove support for server older
MINIMUM_SUPPORTED_SERVER_VERSION
- check if code is outdated due to last supported server version
- Library
- check if code is outdated due to last supported server version
@NextcloudServerannotation - remove support for server older
MINIMUM_SUPPORTED_SERVER_VERSION
- check if code is outdated due to last 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.gradlefile - 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.gradlefile - 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-1branch
- delete
- 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
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de nextcloud/android
-
0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 86/100
nextcloud/android#17845 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Bug] Lock owned by another client (e.g. Text app) cannot be unlocked from the appPosiblemente ocupada @falkloewert la tomó hace 28 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nextcloud/android#17837 · 2 reacciones ·
Los mantenedores suelen responder en 1 día
-
0. Needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
nextcloud/android#17533 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
RC 34.1.0-01: Duplicated wording in creation menu — "New" prefix + creator name produces "New New document" ("Neu Neues Dokument")Posiblemente ocupada @ChristianTannheimer la tomó hace 118 días. Abierto0. Needs triage bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
Todos los issues de nextcloud/android
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Kotlin/kotlin-lsp#309 ·
-
Two stored artist rows are not act names: "DJS" from a Renate floor heading and "Stevie Cox -"Abiertoarea:data-quality importer size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
enorm-labs/event-junkie#5136 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Los mantenedores suelen responder en 1 día
-
Type: Possible bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
spacecowboy/Feeder#1318 ·
Los mantenedores suelen responder en 1 día
-
个人助手回复内容既无法手动选中复制,也没有一键复制Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
wangzan101/Mika#644 ·
Los mantenedores suelen responder en 1 día