Coordinate updates with Mithril/Pallas

Open
  • Is something wrong?
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell
Domain
distributed-systems, documentation

Research direction

No files, tests, or entry points are named. Start by reviewing the listed CIP, DMQ node, Pallas, and Mithril update relationships and any existing project guidance on breaking changes. Done means a clear, agreed process for coordinating these updates is documented.

Written by the indexing model from the issue text.

Description

documentation

[!WARNING]
All breaking changes requires coordinated update of:

  • CIP (n2c + n2n)
  • DMQ node (n2c + n2n)
  • Pallas (only n2c)
  • Mithril (only n2c)

Define a clear process to coordinate update with Mithril/Pallas when breaking changes are introduced.

Dominant language
Haskell
Stars
2
Forks
5
Avg merge
13h 24m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/dmq-node

All issues in IntersectMBO/dmq-node

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.