Release 2.0.0

[tobiasKaminsky]

• Bump version name and version code in all (3) AndroidManifest.xml files
• Update CHANGELOG.md adding new features
• Add Add whats new screen for version 2.0.0 #1282 and test it
• Screenshots/release notes for Fdroid & Google Play #1081
• update translations for Fdroid & Google Play Store

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 4
• Android 5
• Android 6
• Android 7

RC2

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-02
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h) (Currently not possible due to toolchain)

RC3

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-03
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h) (Currently not possible due to toolchain)

RC4

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-04
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h) (Currently not possible due to toolchain)

RC5

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-05
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h)

RC6

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-06
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h)

RC7

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-07
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h)

RC8

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-08
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h)

RC9

• Verify that the new version number is shown in settings
• Tag new version as rc-2.0.0-09
• Build and release to Play Store as beta release and
• Publish it on f-droid as optional release: edit metadata and open new merge request on gitlab
• Verify that it is shown on f-droid (within 24h)

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

• replace screenshots (https://github.com/nextcloud/screenshots/tree/master/android/phone)
• Verify that the new version number is shown in settings
• Verify that logging is disabled
• Tag new version as stable-2.0.0
• Build and release to Play Store as stable release and
• Update Play store changelog based on condensed CHANGELOG.md infos
• Verify that it is shown on f-droid (within 24h) and close unable to start app on cyanogenmod 11 (Android 4.4.4) without GApps #1483
• Publish APK to https://download.nextcloud.com/android/

[tobiasKaminsky]

Although google play console shows still some bugs, I suggest that we release the RC5 as a final within the next days.
Then we can focus on bug fixing for a 2.0.1 and in parallel work on a new feature release 2.1 in parallel as @mario suggested with the "new" git workflow.

What do you think? @mario @AndyScherzinger

[TFLye]

nice idea

[AndyScherzinger]

@tobiasKaminsky In general I'd say yes, but two issues still seem to be critical in my opinion (can't say if they are 2.0.0 only though):

• Sabre\DAV\Exception\BadRequest: expected filesize 1024000 got 552960 #1450
• Can't login to nextcloud with ldap backend #1419 (might be fixed with RC5)

[mario]

@tobiasKaminsky what's the progress on moving all our discussions/ideas to github (from your notebook)? :)

There are quite a few bugs reported (some on Github, some on Play Services, some on Forums) so I'd really opt to fix critical bugs before we release since this is going to be a BIG release, should NOT screw it up.

[tobiasKaminsky]

Transferring from notebook will be next week, currently I am busy on the other project :/
I am trying to fix some bugs now.

[tobiasKaminsky]

@Bubu do you have time to create push RC6 on fdroid? Would be very great 🎉

[Bubu]

@tobiasKaminsky Will do!

Edit: done.

[tobiasKaminsky]

Outstanding issues/prs for RC 7:

• Support for checking if old login is used android-library#90
• new lib release & integrate in master
• add license/source code link #1567
• Show info messages for push #1560
• Make search work again #1539
• Can't login to nextcloud with ldap backend #1419
• Grid view: default to 4 columns #1575

All other bugs are either "need info" or can imho postponed to 2.0.1.
So after finishing this list I would like to do a RC7 and after that the final 2.0.0

@mario @AndyScherzinger

[AndyScherzinger]

Perfectly fine with we 👍

[tobiasKaminsky]

@Bubu can you do another RC release for us on fdroid? RC7 with tag c-2.0.0-07 (https://github.com/nextcloud/android/releases/tag/rc-2.0.0-07)
Thank you 🎉

[Bubu]

@tobiasKaminsky Done: https://gitlab.com/fdroid/fdroiddata/commit/9ec1d7e6a410280335317caffe179b9ab64f7ebf

[enoch85]

Just a quick question, how do I leave the beta program on Google Play once 2.0.0 is released?

[mario]

You'll be automatically upgraded to 2.0.0 stable, but to leave completely:

https://play.google.com/apps/testing/com.nextcloud.client