Squashing bugs and making the software stable will be very important. Within the UI, there are a couple final features and polish. For platfrom there are some key tickets and tasks we want over the finish line.
Release Accoutrements
Team ILL
Priorities: 1. Bugs. 2. Contract Tests. 3. Tech Debt.
1. Bugs
2. Contract Tests
3. Tech Debt
Decided not to do 1108, 966, or 1391.
Why? It's more important to me to have a stable release, even if it contains this tech debt, rather than try to do these refactors and have the system be unstable on release day.
NOTHING!
Bugs should be prioritized however we hope to get through all the tasks as well; Product Grid is the most important feature, and should be worked on first
Tasks in priority order:
BUGS
Please view the following screen shot. If you use the 3.0, UI, Bug filter you will see the bugs in priority rankings. This was the easiest way to copy across.
Sebastian: Questions in: ,
,
- do we even need those 2?
Critical
Not so critical
(Unclear if this will go into sprint)
(Paweł Gesek: I think we could reduce scope here by doing this within the one service you need) Response: yes we could, but I would rather do all the services at once - it's not much work. I wouldn't be putting this into the final pre-release sprint - I don't need this urgently.
to add and prioritize:
Stretch Goals:
Paweł Gesek and Sebastian Brudziński: this report is a must-have for the 3.0 release; if there is another person who can work with Pawel Nawrocki and start this report right away, that would be great. Otherwise please keep an eye on this one.
(Mary Jo Kochendorfer (Deactivated) still needs to clean this up) (Critical) (Sebastian: seems like something is missing in the acceptance criteria)
Anna Czyrko (Unlicensed) Is it really possible to implement this many contract tests in one sprint? It seems like a large number. What about OLMIS-1013 and 1014?