[RELEASE] 2.14

[jesmrec]

TASKS:

• [COM] Ping marketing guys
• [GIT] Create branch release_1.0.4 in owncloud/android-library from master
• [GIT] Create branch release_2.14 in owncloud/android from master
• [DEV] Update version number and name in build.gradle in owncloudComLibrary module
• [DEV] Update version number and name in build.gradle in owncloudApp module
• [DIS] Create changelog file (< 500 chars) and add to CHANGELOG.md in owncloud/android
• [DEV] Add new wizard steps:
  • End of support for <10 servers
  • End of support for <5 Android devices
• [QA] Design Test plan
• [QA] Regression Test plan [WIP]
• [DIS] Generate test APK file from release_2.14 branch in owncloud/android
• [GIT] Create and sign tag oc-android-2.14 in HEAD commit of release_2.14 branch, in owncloud/android
• [GIT] Create and sign tag 1.0.4 in HEAD commit of release_1.0.4 branch, in owncloud/android
• [DIS] Generate final APKs from signed commit in owncloud/android
• [QA] Perform some minor tests in the final apk, including an update from previous version.
• [DIS] Create new release on Github Android repository
• [DIS] Upload & publish release APK and changelog in Play Store
• [DIS] Update screenshots and store listing, if needed, in Play Store
• [GIT] Merge branch release_1.0.4 in owncloud/android-library, into master
• [GIT] Merge branch release_2.14 in owncloud/android, into master
• [SPREAD THE WORD] Write topic in central about the new release
• [COM] Ping marketing guys to write the blogpost
• [GIT] merge release_1.0.4 branch into stable, in owncloud/android-library
• [GIT] merge release_2.14 branch tag into stable, in owncloud/android
• [DOC] Update owncloud.org/download version numbers (notify rocketchat #marketing)

Release communication (and wizard steps):

• Announce deprecation of Android 4.4 (Get rid of Android 4.4 support #2738)
• Announce stop supporting <10 servers ([New arch] Stop supporting <10 servers #2636)

---

Regression test:

https://github.com/owncloud/QA/blob/master/Mobile/Android/Release_2.14.0/Regression_2.14.md

BUGS & IMPROVEMENTS

• (1) Get rid of Android 4.4 support #2738 -> [MOVED to 2.15]
• (2) Duplicated logs [RELEASE] 2.14 #2727 (comment) [FIXED in https://github.com/remove twice log #2746]
• (3) Crash when upgrading from 2.13.1 to 2.14 [FIXED]
• (4) Crash when quota exceeded (not regression) [RELEASE] 2.14 #2727 (comment) [FIXED]
• (5) Shared by link list not updated with items that are not in root [RELEASE] 2.14 #2727 (comment) [CAN NOT BE FIXED HERE]
• (6) Resharing option is not disabled [RELEASE] 2.14 #2727 (comment) [FIXED]
• (7) Lack of error message in uploads with no permission [RELEASE] 2.14 #2727 (comment) [WONT FIX HERE ->
  new arch]
• (8) Account/Client injection fail with multiaccount [RELEASE] 2.14 #2727 (comment) [FIXED]
• (9) crash when sharing after upgrading from latest version 2.13.1 [RELEASE] 2.14 #2727 (comment) [FIXED]

PRs:

• App: [Release] 2.14 #2758
• Library: [Release] 1.0.4 android-library#287

[jesmrec]

(2) [FIXED]

Logs from logcat are duplicated.

1. Open the app
2. Generate some logs by performing some actions
3. Open Settings -> Logs -> Logcats

Current: Duplicated logs
Expected: Every log appears once

Nexus 5X v8

[hannesa2]

Interesting, in my version I don't have duplicated entries. (I use a Pixel 2 Android Q)
Additional I don't have a Nexus 5X.

Maybe you can run my version on a Nexus 5X too.
If with this version there are duplicated too, then it's located to the device.
If not, it's probably your apk. My apk is at least public !

[michaelstingl]

My apk is at least public !

Yeah, thats a disadvantage of the bitrise.io CI we're using for a while. I'd love to have the CI errors and builds public available. @jesmrec Could you post the link to the "Public install page" manually?

@hannesa2 Send me your mail, I'd love to invite you to the bitrise project.

[hannesa2]

@michaelstingl you see it in commits author.
Btw, I see a lot of disadvantages with bitrise. I can't improve/test it with a pull request and it's no more public.

I will stay will Travis, and yes: with x86 tests with Travis.
With Travis I can publish any intermediate release too.

[hannesa2]

#2746 I found the twice logs

[jesmrec]

We worked with Travis for long time. Disadvantages of Travis from our side:

• Long queues to execute the jobs: oC account to support many repos, and waiting times usually took many hours and sometimes more than two days to execute the jobs.
• Timeouts in test execution. For a small set of unit tests is OK. When you have a large set of instrumented tests, execution became even slower and leading to internal timeouts. Unaffordable.

For these main reasons, the team decided to move to another tool. BitRise has also itsown inconvenients (mainly reagarding UI tests), that we are working to fix from our side in several PRs you will find in the list. Currently tests are passing in BitRise, but there are some concerns to agree, in which it is interesting to get more info, like the one i ask you here: #2737 (comment)

We can check if BR allows to make public the final artifacts, if it is really interesting for the community.

Finally, this thread is for the Release 2.14. If you want to comment/discuss other stuff, please use a different issue. Thanks.

[jesmrec]

#2746 I found the twice logs

thanks, i will check.

[michaelstingl]

I can't improve/test it with a pull request

Related? https://devcenter.bitrise.io/tips-and-tricks/use-bitrise-yml-from-repository/