-
Notifications
You must be signed in to change notification settings - Fork 81
1st April 2021
agrimwood edited this page Apr 1, 2021
·
2 revisions
Alex Grimwood AG
Ester Bonmati EB
Zac Baum ZB
Yipeng Hu YH
Shaheer Saeed SS
Adria Casamitjana AC
Yunguan Fu YF
Nina Montana Brown NB
Zhe Min ZM
Bryan Ko BK
Matt Clarkson MC
Qianye Yang QY
Mark Pinnock MP
Remi Delauny RD
Stefano Blumberg SB
Yiwen Li
State of Release - YF
YF - codebase requires further testing
- YF - more in-depth unit testing required to verify functionality
- YF - for example, cross correlation
- NB, YH, YF - discussion regarding update to TF2.4 and associated increase in workload this will require
YH - are there any thoughts regarding current architecture formalism?
- YH - some underlying design principles are required to ensure stability from R1 onwards
- YF - the way loss is constructed needs to be improved prior to R1 (an issue has been raised already)
- NB - significant changes that could be considered architectural alterations should be discussed prior to opening a ticket
YH - detailed ticket assignments and review to be carried out offline
YH - please review the discussion board and encourage people to be pro-active!
- YH - e.g. possibility to include test time training, seeking volunteers (#731)
- ZB/NB - how should the discussion board be used in relation to generating tickets?
- YH - will clarify the utility of discussion board
YH - should meeting schedule be revised?
- YF - possibly to monthly meetings?
- NB/AG/ZB - structure is important, regardless of frequency
- YH - to keep everyone updated
tables: for google docs --> markdown, use tablesgenerator.org
formatting: for google docs --> markdown, use stackedit