Responsibilities » History » Version 2
Sebastian Manger, 02 Feb 2016 10:33
| 1 | 1 | Sebastian Manger | h1. Responsibilities |
|---|---|---|---|
| 2 | 2 | Sebastian Manger | |
| 3 | h2. Environments |
||
| 4 | |||
| 5 | * New Requirements |
||
| 6 | > * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - New |
||
| 7 | > * Responsible: Kurt Gerber (User Stories are complete in form and content; Issues are sorted according to priority). |
||
| 8 | > * Hosting: None |
||
| 9 | > * Notes: Application errors are new user stories as well - they might just be on the top of the list. |
||
| 10 | |||
| 11 | * In progess |
||
| 12 | > * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - In Progress |
||
| 13 | > * Responsible: Developers (Lukas / Sebastian) |
||
| 14 | > * Hosting: https://qcat-dev.wocat.net |
||
| 15 | > * 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. |
||
| 16 | |||
| 17 | * Review |
||
| 18 | > * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - Resolved |
||
| 19 | > * Responsible: Kurt Gerber / Project Management |
||
| 20 | > * Hosting: https://qcat-beta.wocat.net (to be defined) |
||
| 21 | > * Notes: Review should be done after each sprint. Kurt Gerber decides if the PM must also review a feature. |
||
| 22 | |||
| 23 | * Done |
||
| 24 | > * "Agile Board column":https://redmine.cde.unibe.ch/projects/qcat/agile/board - Feedback |
||
| 25 | > * Responsible: Developers |
||
| 26 | > * Hosting: https://qcat.wocat.net |
||
| 27 | > * Notes: If an issue is done, it must be deployed to the live environment. |
||
| 28 | |||
| 29 | h2. Workflow: new requirements and application errors |
||
| 30 | |||
| 31 | * The review must only check for the defined acceptance criteria |
||
| 32 | * If new requirements are asked for, a new subtask is created. The new issue is treated as any other issue. |
||
| 33 | * If an application error occurs, Kurt Gerber decides on its priority. |
||
| 34 | > * If it must be resolved immediately, a hotfix is created. |
||
| 35 | > * A hotfix also results in a new task and is reviewed. |
||
| 36 | > * The hotfix is merged into the beta-branch first. |
||
| 37 | |||
| 38 | h2. To be defined: |
||
| 39 | |||
| 40 | * How do we implement these responsibilities? |
||
| 41 | * Beta and live deploy: |
||
| 42 | > * do we use git tags? |
||
| 43 | > * manual deploy with a defined release calendar or integrated with the continuous delivery system? |
||
| 44 | |||
| 45 | h2. Tools: |
||
| 46 | |||
| 47 | * "Opbeat":https://opbeat.com/university-of-bern-cde/ measures the performance and logs all errors. |
||
| 48 | * "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). |