[Epic] Maintenance

[richard-ramos]

Summary

Maintenance items that do not directly fit under any other milestones, yet need to be done to avoid problems.
Typically:

• dependencies update (so that we do not wait to need the upgrade to do it)
• bugs reported by users of go-waku
• Releasing

RAID (Risks, Assumptions, Issues and Dependencies)

• This may become a dumping ground, let's thrive to not let this happen.

[richard-ramos]

Weekly Update

• achieved: improved keep alive logic for identifying if machine is waking up; added vacuum feature to sqlite and postgresql; made migrations optional; refactored db and migration code, extracted code to generate node key to its own separate subcommand

[richard-ramos]

Weekly Update

• achieved: refactored wakuv2 metrics to make each protocol responsable for registering and defining its own metrics

[harsh-98]

Weekly update

• achieved: refactoring and some bug fixes in peermanager and read rfcs and docs
• next: increase test coverage and read more code.

[richard-ramos]

Weekly Update

• achieved: allow mixing named and static shards, logs succesful message pushes, concurrency fixes for filterv2

[richard-ramos]

Weekly Update

• achieved: add tls/ws to address factory and log ENRs only after they have been setup

[harsh-98]

Weekly update

• achieved: rln membership registration logic refactoring and fixing bugs . Added test for membershipFetcher. Added code for mock_blockchain and mock_client to test membershipFetcher.

[chaitanyaprem]

Weekly update

• achieved: fix panic observed in peer-manager, update filter protocol as per rfc.

[harsh-98]

Weekly update

• achieved: CommonService for embedding lifecycle operation in lightpush,discv5,filter,peerConnector etc.
• next: after discussion with richard prem, use create 2 different types of commonService. Change nameServer flag functionality in go-waku to nwaku. And work on newly created tasks.

[fryorcraken]

Maintenance work does not need to be tracked with an Epic. Ref: waku-org/pm#91