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
{{ message }}
Repository navigation
RabbitMQ service: the guide, docs/rabbitmq-service-guide.md (spec 023) #543
Spec 023 (docs/specs/023-rabbitmq-service.md) asks for docs/rabbitmq-service-guide.md, and none of its build issues (#505 to #512) carries it; PR #540 left it out for that reason.
The spec's Documentation section sets its content: it opens with what a backup does not hold (no message), then covers declaring one node, growing to three, what an application lists in its client, publisher confirms and manual acknowledgements, which queues are copied and which are not, a version change inside a series and to the next one, replacing a lost node, what a team sees while the cluster has no majority, and restoring definitions from an export. ROADMAP.md and ARCHITECTURE.md name the kind.
It describes what #508, #509, #510 and #511 build, so it waits for them.
Writes the guide spec 023's Documentation section asks for, for #502, as the body above scopes it. It starts once #509 and #510 close, since it describes their rolling changes and node replacement; its Depends on lines hold it until then. Its PR also adds this issue to the spec's Issues section. I'll link the PR here.
Activity
shipmill-romamo commentedon Nov 18, 2026
Triage: implement. Serves: G-1, G-3.
Writes the guide spec 023's Documentation section asks for, for #502, as the body above scopes it. It starts once #509 and #510 close, since it describes their rolling changes and node replacement; its
Depends onlines hold it until then. Its PR also adds this issue to the spec's Issues section. I'll link the PR here.