Closed Ein-Tim closed 2 years ago
@All, we are working on a statement about the approach to planning and implementing features in the app. Please keep in mind that our objective is to stay as up-to-date as possible with the app. However, development (including testing) will always lag behind the current decision-making process. So, yes, we are aware that the released version may not always reflect national and/or regional rulings or dynamically changing decisions and recommendations of the authorities. Obviously, we will not and cannot implement and publish anything that has not been approved by the stakeholders and the necessary legislative authorities (including BfDI).However, in the interest of time, we try to parallelize some activities within the SCRUM approach. In rare cases, this may also lead to redundant coding, but in terms of risk assessment, we accept this risk to be able to ensure timely delivery.
Be assured, we will use the momentum and we are on track to cover the ongoing legislative amendments with the next versions of the app.
Please remain patient.
@GisoSchroederSAP Thank you for letting us know that you are working on a statement! Enjoy Friday & your weekend!
Closing as the DCC ticketing feature was put on ice: https://github.com/corona-warn-app/cwa-website/issues/2218#issuecomment-1094809124.
Your Question
As announced in the blog post Corona-Warn-App simplifies certificate checks when booking tickets, since version 2.15, the app offers the so called DCC ticketing feature. This feature was implemented in version 2.15, although the BfDI had and still has not finished their audit of this feature yet.
When asked on Twitter, why this was implemented, someone working at the BfDI responded:
As the development team is in close contact with the stakeholders (RKI/BMG), the following questions arise and could be internally clarified and then answered here: