Skip to content
This repository has been archived by the owner on Mar 30, 2021. It is now read-only.

Update readme #36

Merged
merged 3 commits into from
Mar 30, 2021
Merged

Update readme #36

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
34c16bb
Update README.md
dsarkar Mar 29, 2021
1e04554
Update README.md
dsarkar Mar 29, 2021
8f757d4
Update README.md
dsarkar Mar 29, 2021
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
11 changes: 11 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,17 @@

## About this Repository

This backlog repository was archived on March 30th, 2021. All issues from the backlog repository, including the closed ones, have been transferred to active repositories, i.e. no issue has been lost. For reasons of transparency we have archived this repository in preference to deleting it. This allows previous links to issues in the backlog to continue to work, due to GitHub's automatic re-direction to the transferred issue in its new repository location.

Why has this repository been archived? For some time the backlog repository had not been used for its original purpose and instead issues are usually taken care of in the repository where they were created. Keeping issues in the original repository has the advantage of not mixing up Android, iOS, documentation, website and wish-list items together with other issues.

Archived repositories are read-only. Closed issues in an archived repository can be read, but not re-opened or commented on. Therefore, by transferring issues from the backlog repository to other active repositories we allow the community to comment and re-open closed issues if necessary.

Originally the backlog repository was intended to show issues in the pipeline of being solved. Instead, we now mark issues in the active repositories with labels "Fix" + release number to show that there is a plan to fix the issue. This means that the issue has a corresponding internal development status which is one of OPEN, ANALYZING, IN PROGRESS, COMPLETED or CONFIRMED (i.e. tested). The Fix label stays with the issue even after the fix has been released and the issue has been closed.


## About this Repository (Original text)

This repository contains future improvements of the Corona-Warn-App that will be implemented for the next app releases.
Please note that this is not a *complete* backlog but a communication of a subset of planned extensions where we more or less know that they are coming.

Expand Down