Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#36 Adds detailed bug example #37

Merged
merged 4 commits into from
Feb 12, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -332,6 +332,25 @@ v10 or iPhone 8 view.
Then take a screenshot of the bug and put it all into an issue to be fixed
:wrench: :sparkles:.

**Here is an example of an issue that contains a description of the bug, the
critical steps required to reproduce it and which devices it was experienced on:**

![image](https://user-images.githubusercontent.com/16775804/35097023-4900501c-fc46-11e7-9856-0387d1f64d17.png)

Taken from: https:/cul-2016/quiz/issues/582

## What is a staging area/site and what is it used for?

A staging site is a replica of your live (aka production) website. It is used as
a first stage for testing when you deploy new code / features. It acts as a
testing ground so that errors can be caught and fixed before finally deploying
and updating the live site. Your staging site is meant for internal not public
use.

![image](https://user-images.githubusercontent.com/16775804/35052543-bb723914-fb9f-11e7-96f4-4e91732dda5e.png)



## Timing demos and deployments

The PO and the Scrum Master liaise with one another to find a time and day suitable for sprint demos and deployments. We do however recommend the following on all occasions:
Expand Down