release-plan

To build a release plan from GitHub issues, the planner collects open issues labeled verify-done, filters out already planned work, and groups them into structured release units based on priority and size.

Yes, you can group GitHub issues into releases by priority and size. The planner identifies P1-P3 priorities and XS-M-L sizes to filter and group items into structured release units for versioning.

Epic handling and dependency analysis affect release planning by respecting epic and dependency relationships to generate coherent, dependency-aware release bins that ensure a logical implementation order.

The best way to structure release scope and implementation order from issues is to assemble coherent release bins that produce a finalized plan document outlining per-release scope, issue lists, and execution order.

No, the release planner does not work with issues not labeled verify-done. It specifically collects open GitHub issues with the verify-done label to filter out already planned work and group the remaining items.

Your release plan excludes certain open GitHub issues because the planner filters out issues lacking the verify-done label and removes already planned work to assemble coherent, dependency-aware release bins.