You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elias Rohrer edited this page Aug 8, 2022
·
1 revision
Chair: @devrandom
Attendees
ariard
devrandom
jkczyz
arik-so
Matt Corallo
Valentine Wallace
Brian Mancini
Current Work
0.0.13 (#752/#646/#761/#762)
node sample (#763)
Discussion
Progress a bit slow due to holidays.
PR standards:
When to put PRs in milestones: when they block the release. PRs that are not a deliverable for any particular release will remain without milestone assigned (but can still be high priority for other reasons - e.g. important cleanup).
smaller PRs (but not always possible)
a couple of people felt that some review items can be postponed to followup PRs
"Standard of care" for PRs: For new subsystem like gossips or routing improvements, okay to be less-than-perfect.
For critical code paths, state machine, onchain, key management, "production quality" readiness.
While working through a PR, author may create a followup PR with followup tasks that are not critical for keeping master solid.
@jkczyz to split 763 (node sample and block sync) into bite size chunks and hopefully parallelize.
Need to "write down more" - maybe the new wiki will encourage.