IntersectMBO / IntersectMBO/cardano-node

Release v11.2

Open
#6,672 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Haskell
Stars
3.2k
Forks
754
Avg merge
4d 20h
Merged PRs (30d)
20

Description

Ticket tracking the progress of release 11.2. The table below is meant to show the status of the integration branches at a glance - I will keep it up to date as things evolve.

# Release Process for Cardano Node vX.Y.Z

| Component | PR | Status |
|----------------------------------------------------------------|---------------------|-------------------|
| [kes-agent](https://github.com/input-output-hk/kes-agent) | https://github.com/input-output-hk/kes-agent/pull/106 | CHaP release required |
| [Ledger](https://github.com/IntersectMBO/cardano-ledger) | https://github.com/IntersectMBO/cardano-ledger/pull/5999
https://github.com/IntersectMBO/cardano-ledger/pull/6051 | In progress (missing PV4 ScriptContext) |
| [Ouroboros Consensus](https://github.com/IntersectMBO/ouroboros-consensus) | https://github.com/IntersectMBO/ouroboros-consensus/pull/2228
https://github.com/IntersectMBO/ouroboros-consensus/issues/2295 | In progress |
| [Cardano API](https://github.com/IntersectMBO/cardano-api) | https://github.com/IntersectMBO/cardano-api/pull/1328 | In progress |
| [Cardano CLI](https://github.com/IntersectMBO/cardano-cli) | https://github.com/IntersectMBO/cardano-cli/pull/1439 | In progress |
| [Cardano Node](https://github.com/IntersectMBO/cardano-node) | https://github.com/IntersectMBO/cardano-node/pull/6677 | In progress |

## Dependency Tree

```mermaid
flowchart BT
A[Plutus]
B[Ledger]
C[Ouroboros Network]
D[Ouroboros Consensus]
E[Cardano API]
F[Cardano CLI]
G[Cardano Node]

B --> A
D --> B
D --> C
E --> D
F --> E
G --> F

%% Javier added

H[cardano-base]
I[kes-agent]
J[cardano-config]
K[cardano-keys]
L[hermod-tracing]

B --> H
I --> H
D --> J
D --> K
D --> L
D --> I
C --> L
J --> L
```
- An arrow means "depends on"

Contributor guide

Open the contributing guide

Research direction

Start with the component PRs and issues linked in the release table, then review the dependency tree to understand the release order. Done means the v11.2 integration statuses and required release work are complete and the tracking table is up to date.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
release
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.