WOCAT » QCAT

h1. Responsibilities

h2. Environments

* New Requirements

> * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - New

> * Responsible: Kurt Gerber (User Stories are complete in form and content; Issues are sorted according to priority).

> * Hosting: None

> * Notes: Application errors are new user stories as well - they might just be on the top of the list.

* In progess

> * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - In Progress

> * Responsible: Developers (Lukas / Sebastian)

> * Hosting: https://qcat-dev.wocat.net

> * QR Code !qcat_dev.png!

> * Notes: User Stories result in feature branches; Continuous delivery is active for the develop branch only. If a feature is finished, the issues status must be updated on redmine.

* Review

> * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - Resolved

> * Responsible: Kurt Gerber / Project Management

> * Hosting: https://qcat-beta.wocat.net (to be defined)

> * QR Code !qcat_beta.png!

> * Notes: Review should be done after each sprint. Kurt Gerber decides if the PM must also review a feature.

* Done

> * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - Feedback

> * Responsible: Developers

> * Hosting: https://qcat.wocat.net

> * QR Code !qcat_live.png!

> * Notes: If an issue is done, it must be deployed to the live environment.

h2. Workflow: new requirements and application errors

* The review must only check for the defined acceptance criteria

* If new requirements are asked for, a new subtask is created. The new issue is treated as any other issue.

* If an application error occurs, Kurt Gerber decides on its priority.

> * If it must be resolved immediately, a hotfix is created. 

> * A hotfix also results in a new task and is reviewed.

> * The hotfix is merged into the beta-branch first.

h2. To be defined:

* How do we implement these responsibilities?

* Beta and live deploy:

> * do we use git tags?

> * manual deploy with a defined release calendar or integrated with the continuous delivery system?

h2. Tools:

* "Opbeat":https://opbeat.com/university-of-bern-cde/ measures the performance and logs all errors.

* "Shippable":https://app.shippable.com/ is used for continuous delivery (deploys the latest state of the develop branch to qcat-dev if all tests pass).