Updated team's documentation
how to give great code review feedback
more notes on how to test stuff
@@ -23,6 +23,8 @@ It should use the same version that was built in the previous step.
- Smoke test (no tasks are run): ```./gradlew testRelease -m```
- Test most things, without actually making any code pushes/publications: ```./gradlew testRelease -x gitPush -x bintrayUpload```
- Release notes content: ```./gradlew previewReleaseNotes```
+ To generate sizable release notes content, before running 'previewReleaseNotes' you can downgrade the 'previousVersion' in 'version.properties'.
+ Release notes are generated from 'previousVersion' to current 'version' as declared in 'version.properties' file.
4. Advanced testing (occasionally, for core developers, edge cases):
- Release notes in file: ```./gradlew previewReleaseNotes```, then inspect updated file
- Test release needed task: ```./gradlew assertReleaseNeeded```
