CCU2 Release Toolkit

Release Management,
Simplified.

From GitHub commit lookup to patch cherry-pick tracking and deployment verification — everything you need for CCU2 release work in one place.

Get Started
CORE FEATURES
CCU2 Patch List

Query commits added to master after the base tag and track cherry-pick status. Commits already applied to the branch are auto-detected via diff-based Patch ID comparison.

Merge Keep No Need Patch ID Auto-detect
Merge Verification

Verify the list of commits actually included in the deploy tag range and check that all commits marked as Merge are present without gaps. Shows ✅ Ready to Deploy when all commits are verified.

Merge ✓ Keep ✗ No Need ✗ Direct ✓ No Decision
Git Change List

View commit change history between two release tags at a glance. With Jira integration, Automated Test and Customer Notify info is shown alongside.

Notify: YES Notify: N/A Jira Integration
Decision Management

View all Merge / Keep / No Need / Direct decisions recorded per branch and delete any incorrectly recorded entries.

Branch Filter Decision Filter
Patch ID Detection
Precise, No False Positives
Why Patch ID Comparison?
✗ commit hash Cherry-picking changes metadata (date, author), so the hash always differs
△ commit message Risk of false positives when the same message is used across multiple commits
✓ Patch ID Only diffs are SHA1-hashed — identical changes are detected even if metadata differs. The standard method used internally by git cherry.
RELEASE WORKFLOW
1. Register Branch
Register the release
branch in Branches
2. Review Patch List
Record Merge /
Keep / No Need per commit
3. Cherry-pick
Apply commits
to the branch
4. Verify
Final check for missing
commits by deploy tag