Release 3.27.0

[tobiasKaminsky]

**Planned RC1: 04.12.2023
Planned Release date: 12.12.2023

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_VERSION according https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule (e.g. NC12)
  • MINIMUM_SUPPORTED_SERVER_VERSION: fix to NC16
  • 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 @NextcloudServer annotation
  • remove support for server older MINIMUM_SUPPORTED_SERVER_VERSION
  • lower minimum version for FileUploader:useFilesUploadWorker(…)
• 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

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
  • 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 major 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 6
• Android 7
• Android 8
• Android 9
• Android 10
• Android 11

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:

• App
• Library

Open PRs:

• Milestone

Marketing:
@jospoortvliet

[exstntlmsnthrp]

I've tried downloading and installing numerous times, all with the same results. Reverting back to previous install and I have no issues.

[exstntlmsnthrp]

@joshtrichards Thanks kindly for informing me of that! I had no clue. It was more annoyance directed at GitHub than you folks (though I can see you wouldn't necessarily know this 🤦🏽‍♂️) as they have historically been slow to update their mobile app.

I didn't take issue with the form itself, as I can appreciate that has the potential to standardize reporting and hopefully making it easier for devs.

It was more about hopping into the web browser, needing to re-login, and then the web UI took 5 or 6 seconds to adjust from the desktop version to mobile.

It just wasn't a smooth experience.