Editor Group 12.3 Release
12.3 Release Board
Overview -In 12.2 the primary focus was continuing to improve our capabilities around indexing for Elasticsearch and working on search performance improvements. There were also some updates to the Web IDE to improve the editing experience.
Some time was also spent during the milestone evaluating Theia as an alternative and replacement to the existing Web IDE.
In 12.3 the primary focus will be on continuing to improve the experience around Elasticsearch indexing and performance improvements for search. There will be a large focus on implementing new administration screens and producing some new data for those screens.
There are also some P1/P2 bugs that need to be addressed in search.
UX
Please see the UX Board for this release
- UX Weight: TODO
Frontend
Please see the FE Board for this release
- FE Weight: TODO
Backend
Please see the BE Board for this release
- BE Weight: TODO
Product process checklist
Notes to self, and to help me document my process for new PM's as they join. I typically work through these boards and issues, in the order listed below grooming the issues.
Boards
- Create groups for milestone - make sure every issue in the milestone has the correct group assigned
- Editor Deliverables / Stretch / NPR for milestone - quick view of what is/isn't deliverable, pretty much everything non-deliverable should be removed from the milestone by kick off to prevent confusion that it will be implemented
- Editor BE / FE / Discovery for milestone - make sure very issue has either BE, or FE, or both assigned
- Create groups for HackerOne - make sure every HackerOne security issues has the correct group assigned
- Bugs
Lists
- Security issues sorted by due date - make sure all security issues with an upcoming due date are assigned to meet our security SLA
- Bugs
Checklist
-
Groom the issues already assigned to the current milestone for correct label hygiene -
Check/update past milestones for wayward issues -
Check/update relevant category visions (snippets, Web IDE, Search, Live Coding) -
Add vision items -
Add security items -
Add bugs -
Carefully check ~promised items for customers are scheduled or well communicated