\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
\uD83E\uDD45 Goals
To define the Sprint n.8 for release v1.13.0
\uD83D\uDDE3 Discussion topics
Time | Item | Presenter | Notes | ||||||
|---|---|---|---|---|---|---|---|---|---|
21:00 CEST | Next release 1.13.0 | We briefly discussed the status and roadmap of the project and the reason why this new release is so close to the previous one. The GUI project is going to an end, in favor of the new UI, but this will still take a lot of time that is difficult to estimate, because it dependes by the opensource community and also because it is hard to switch the interface from a day to another; so there will probably a span of time when the two will be both available, until the UI will cover 100% of the current GUI. Moreover some feature are going to be developed for the UI only and not for the GUI and viceversa, caring mostly about mutual compatibility. A new version 1.13.0 so close to the previous one (1.12.0 released on February) is due to a project constraints, for which GDPR, Dashboard and Patient Portal have to be released together at the end of June 2023. miz about the roadmap pointed out that, in some extend, to have a completely “standalone” software solution has still a big value in some context and that also we are at the moment expanding the offer developing new services like the Patient Portal and it is in some extend the way to go and to focus most. Moreover GUI is at this moment covering 100% of our installations, so this is a fact we cannot ignore and so we have to still support its development, until we are totally sure the UI (together with its CORE+API stack) will be ready and fully under control (Jetty issue). David B Malkovsky also points out that for low resource consumption places, the GUI is probably the way to go for quite a while. | |||||||
21:20 | Sprint n.8 | @All | The team decided to add a number of issues for a total of GDPR issues are many and we are already OK for the release of June with the ones
Patient Portal side requires the Patient Consensus Management (OP-1035), so we included it although it needs a re-design of the “Administrative Consent” so it will require a little bit of development still. Finally, we included the issue about JWT upgrade, because it sounds very related to the Security topic, and two small recent bugs. miz Nice to have: to provide an high definition logos to include in the package because the one we have are a bit blurred. | ||||||
22:00 | Issues out of this Sprint | @All | We decided to move all remaining issues tagged as 1.13.0 after the sprint to a new tag 1.14.0 (so we can have a starting point) and we will do another call after the release to revise them together with the ones without any tag. miz suggest to have a look at the oldest and we can also decide to have dedicated sprints where we focus only on the 10 or 20 oldest issues every time. David B Malkovsky suggests also to clean the backlog by calling out the issues that are too old and maybe not a problem anymore or the ones that we won’t fix. | ||||||
22:15 | Administrative Consent (OP-1038) | We briefly discussed the need to change the requirement for Administative Service Flag (OP-1038) |
✅ Action items
- Alessandro Domanico to create Sprint n.8