Feature/dra 141

.circleci/config.yml

@@ -3,9 +3,10 @@ jobs:
   build:
     working_directory: ~/code
     docker:
-      - image: circleci/android:api-29
+      - image: circleci/android:api-30
     environment:
-      JVM_OPTS: -Xmx3200m
+      JVM_OPTS: -Xmx8192m
+      GRADLE_OPTS: -Xmx8192m -XX:+HeapDumpOnOutOfMemoryError -Dorg.gradle.caching=true -Dorg.gradle.configureondemand=true -Dkotlin.compiler.execution.strategy=in-process -Dkotlin.incremental=false
     steps:
       - checkout
       - restore_cache:

.gitignore

@@ -1,14 +1,13 @@
 *.iml
 .gradle
 /local.properties
-/.idea/caches
-/.idea/libraries
-/.idea/modules.xml
-/.idea/workspace.xml
-/.idea/navEditor.xml
-/.idea/assetWizardSettings.xml
+.idea/*
 .DS_Store
 /build
 /captures
 .externalNativeBuild
 .cxx
+*.apk
+*.aar
+*.ap_
+*.aab

CHANGELOG.md

@@ -0,0 +1,9 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [1.0.0](https://github.com/JimClermonts/Kotlin-Android-sample-App/releases) - In progress date
+-   Initial release.

CONTRIBUTING.md

@@ -0,0 +1,28 @@
+# How to Contribute
+
+We encourage you to participate in this project. We love pull requests, bug reports, ideas, (security) code reviews or any kind of positive contribution. Please feel free to post questions, recommendations, ideas, bugs by create [new issue](https://github.com/JimClermonts/Kotlin-Android-sample-App/issues/new)
+
+## Code reviews
+
+All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more information on using pull requests.
+
+After that create your [pull request](https://github.com/JimClermonts/Kotlin-Android-sample-App/compare) and complete the template structure adding any information that you consider relevant, to make it easier to identify these changes.
+
+## Code quality
+
+Once the pull request is created, make sure that it passes the different static analysis checks and tests. Otherwise review the errors in the build and make the necessary changes to correct it.
+
+## Code release process
+1. Checkout `develop` branch with `feature/number_of_jira_ticket`.
+2. Work on task and make small commits.
+3. Try to add a couple of tests, start with unit tests and go up the pyramid.
+4. When done, run the existing test cases to make sure everything still works:
+
+`./gradlew testDebugUnitTest`
+
+`./gradlew connectedDebugAndroidTest` 
+
+5. When all tests still work, create pull request.
+6. Wait for review of team member and make changes if necessary.
+7. Make a test build and share it with the tester.
+8. When no changes need to be made, merge the `feature` branch with the `develop` branch and delete the branch.