From 34c16bbfa8147f65a1c7f53bde84579a7d2360ca Mon Sep 17 00:00:00 2001 From: dsarkar Date: Mon, 29 Mar 2021 18:50:13 +0200 Subject: [PATCH 1/3] Update README.md --- README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/README.md b/README.md index e262d21..9310617 100644 --- a/README.md +++ b/README.md @@ -4,6 +4,17 @@ ## About this Repository +This backlog repository was archived on xx/xx/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 is either still OPEN, ANALYZED, IN PROGRESS, COMPLETED or CONFIRMED (i.e. tested). + + +## 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. From 1e045544758645aee31799a44c567b6cdeb9acee Mon Sep 17 00:00:00 2001 From: dsarkar Date: Mon, 29 Mar 2021 18:53:29 +0200 Subject: [PATCH 2/3] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 9310617..1e5affe 100644 --- a/README.md +++ b/README.md @@ -10,7 +10,9 @@ Why has this repository been archived? For some time the backlog repository had 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 is either still OPEN, ANALYZED, IN PROGRESS, COMPLETED or CONFIRMED (i.e. tested). +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) From 8f757d4f8b30217e0520bcfe8206b29e51c2fa2d Mon Sep 17 00:00:00 2001 From: dsarkar Date: Mon, 29 Mar 2021 19:06:28 +0200 Subject: [PATCH 3/3] Update README.md --- README.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1e5affe..59df720 100644 --- a/README.md +++ b/README.md @@ -4,15 +4,13 @@ ## About this Repository -This backlog repository was archived on xx/xx/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. +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. +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)