Progress review agenda 29 March 2022
Hi @lathrops1 @Kireev @latternm @ErinS @deniskar
(cc @John.kopanas @danjela @DioneMentis @sidorelauku @bela @vignesh03 @andynicholson @Shanthi_B @pokhi @shubtiwari)
Progress update
We are starting the March C milestone tomorrow. Our team is still estimating the total time required. We are focussing on priority bugs since we don't have a new feature ready to develop yet.
We are planning on doing a release tomorrow which should include all fixes related to cover submissions as well as fixes to metadata and ordering in collections.
QA testing
We have mapped out all the required tests and our team is starting to write tests this week. We will confirm in next week's update a list of files we'll require from the NCBI for this testing.
Things that we are focussed on resolving for development
- #701 (closed) - we will have questions for NCBI this week
- We want to focus on finishing development on Collection TOCs-related work. In order to progress we need the NCBI to confirm approach in #1076 (closed) and answer this question in 992.
- The last remaining feature for Collection TOCs is also pending the finalised proposal from the NCBI in Issue 1088.
- #211 (closed) – repeating TOC entries: the design is in progress with our UX designer.
- #508 (closed) – since NCBI has requested the vendor issues to be included in deployment 1, this related design work is going ahead this week.
NCBI feedback
We are interested in the NCBI's feedback on agreements API testing and the review of the errors management proposal as discussed in the last meeting.