View Source

GoRead Release Cycle for a release candidate

\- Ask for user guide (Deanna) and push it


\- Last code change has been submitted via a pull request to the repo ([https://github.com/benetech/FBReaderJ]) (Developer)


\- Code freeze

\- Increment the version code inside the build.gradle file and commit.  The version code needs to be incremented by 1.  Google play store will reject apk if it has same version code as what there now (Developer)

\- Initiate a jenkins build via: [https://build.benetech.org/view/GoRead(FBReaderJ)/job/FBReaderJ/] (Developer or Systems via new jira ticket)

\- Once the build is successful, the apk will be placed under [https://artifactory.benetech.org/libs-snapshots-benetech/] (Developer)

\- Download the apk to your local drive (Developer)

\- Log into google play store developer console [https://play.google.com/apps/publish/|https://play.google.com/apps/publish/??] (Developer)

\- Go the release management section \-> App releases \-> Manage Alpha \-> create release (Developer)

\- Upload the APK (Developer)

\- Alpha version is tested (QA Team)

\- GoRead play store landing page has been updated (Deanna or Ginny)

\- Create systems ticket to push alpha to live.  In order to create a chain of deployment jiras, the new jira must be cloned from the last deployment jira (example [https://bugs.benetech.org/browse/SYS-2849]) (Systems)

\- Tag a release in github (https://github.com/benetech/FBReaderJ/releases)