Closed kdahlquist closed 7 years ago
@anuvarsh has made some progress and will have time until next Wednesday, after which she needs to focus on MCAT. The goal we have established is for her to have the functionality working with refresh. We will look into making normalization adjustments without refresh after that, for the remainder of the semester.
@mihirsamdarshi was momentarily stuck but @dondi advised him to keep his developer console open so he can see any errors that were emerging, which was what was happening in this case. Upon seeing the error, this immediate issue was fixed during the meeting and he can now proceed.
He is projected to be finished with #355 well before the next technical meeting, so @dondi asked him to proceed to #381 once #355 has been finished, pull-requested, reviewed, and merged.
@eileenchoe is on the verge of issuing a pull request for #362, which @dondi will review. She also has a general approach (similar to @ebachoura's) for handling empty files (#428).
For @ebachoura, @dondi walked through the process involved in implementing #363, ranging from the tests to how to handle the err
argument passed by the third-party parseString
function. @eileenchoe's existing unit tests for her SIF syntactic checker can serve as a pattern for his own unit tests.
@dondi relayed to @eileenchoe and @ebachoura that we will be entering a swarm phase to help @NAnguiano with QA-ing her 402 work. At certain milestones, @NAnguiano can ask @eileenchoe and @ebachoura to do a thorough test with all of the combinations for the zooming/bounding box/adaptive settings that she is implementing. @eileenchoe and @ebachoura can report issues and potentially offer fixes to help polish the work.
Updated task list for @ebachoura and @eileenchoe to assign #364 as per @NAnguiano's request. Downgraded their other tasks in the meantime.
Updated task list to add #417 to @ebachoura and @eileenchoe.
@NAnguiano and @yshin4, any progress to report after today's work session?
@NAnguiano expects a new pull request for her features tonight.
I closed #396, #399, and #411, opening a slew of more granular issues instead. They have been all marked with a priority level and whether they are for the upcoming release. I'm not going to try and update this issue right now. So, @NAnguiano, just please apply the relevant label filter to see what needs to be fixed immediately.
I'm closing this. All open tasks that need to be completed for the next release are labeled as such. Further notes will go on issue #422: checklist for release.
For @anuvarsh
For @yshin4 (generally in the vein of tidying up the graph layout features/bugs)
For @mihirsamdarshi
For @eileenchoe
For @ebachoura
For @NAnguiano
For @kdahlquist
For @dondi