Proposal to elect new release rc--2024-06-26_23-01

Thanks for providing more info @sat.

I’ve had the impression that the build system isn’t the most reliable judge for what changes are actually modifying the target system for a specific proposal. This came up a few weeks ago when discussing why the proposal summary generation tool needs to filter various things out.

Other tooling limitations don’t appear to be uncommon.

The boundary node firewall caught my eye because firewall changes have previously been deployed via GuestOS proposals. I’m curious why some firewall changes take effect via HostOS proposals and others via GuestOS (which runs inside a VM spun up by HostOS). It’s not too important, but if someone from the node team is able to take 5 mins to clarify/explain this, that would be awesome.

The change to the registry canister is another example (mentioned in my first post above). I don’t believe that change actually modifies GuestOS behaviour - does it?

Would I be overstepping if I created a new forum topic with an aim to discuss and brainstorm ways of making proposal summaries more reliable and/or easier for the community to follow/understand/validate? I think this sort of conversation spans more proposals than just this weeks ones. Having a consistent place to catalogue proposal accuracy issues and discuss/rule out potential ways to improve things would be useful (I hope other in the community may get involved also - hopefully constructively).

3 Likes