Triage Meetings: April 5 & 7, 2022. Release 3.0.0 alpha - Seneca-CDOT/telescope GitHub Wiki

Sheriffs for the week:

  • Diana Belokon
  • Thanh Van

PRs:

  1. #3373 - needs one more review, and Tue needs to improve on the feedback
  2. #3371 - Draft, Tim is going to follow up with the improved code after code reviews
  3. #3363 - assigned 4 reviewers
  4. #3420 - needs reviews, waiting for James to respond to the code reviewers. Not passing lint, need to do some formatting fixing
  5. #3419 - lots of feedback, Tue will follow up with the requested changes
  6. #3418 - Needs a meeting for more discussion (Kevan, Dave + anyone who is interested in Database, Prisma stuff)
  7. #3417 - assigned reviewers
  8. #3416 - needs one more review from Tue
  9. #3414 - needs reviews, added a few more people to do the review
  10. #3413 - Tue is going to follow up with the changes based on the requested changes
  11. #3411 - Draft
  12. #3405 - Jerry clarified some things with Dave, should be good to finish the PR
  13. #3404 - just one more review is needed. Assigned one reviewer. It is basically done.
  14. #3371 - Draft, needs more time, because it is being hold up by the legacy backend PR thingy
  15. #3363 - still needs one more review, should be good to go
  16. #3335 - Draft, needs a lot of debugging, moved to Release 3.0. Tricky bug
  17. #3307 - moved to Release 3.0

Important announcements:

  • Release 3.0 is pushed to be released on April 21st.
  • Tried doing live reviews, kind of cool and makes it easier to review when the person who wrote the code goes through it and you can ask questions right away. Might be time consuming though, so we have to find a way to go through more PRs like that.
  • Some issues must be fixed before 3.0.
  • Did the demo for big PRs - Roxanne did the demo for 3416, 3414. Tue did a demo for 3413.

Insightful thoughts (Thanks to Dave):

  • Every 10 lines of code add another bug

Great idea to focus on release 3.0 (thanks to Alex):

  • Finish everything that you started (main features that you owned, etc)
  • Write a documentation/make a video or some sort of guide so that after you leave, others will know how to navigate easily.
  • If you can’t finish something that you own, file issues for what’s left to be done.