releases
Releases Guide
This guide covers release conventions and guidelines for AG Charts.
Release Schedule
- Releases are typically monthly for minor releases, and 6-monthly for major releases (typically in June and December).
- Patch releases are typically only for critical bug fixes, at most weekly.
Release Constraints
- Minor releases cannot have breaking changes, we must hold these back for major releases.
- Deprecations are allowed, but must be clearly marked as deprecated and still work as before.
- Deprecated features/options are typically immediately removed from public website documentation to discourage use.
Release Branch Naming
- Release branch names are of the form
b12.0.0
More from ag-grid/ag-charts
estimate-jira
Estimate complexity, effort, and risks for JIRA tickets, features, or projects. Generates structured reports with time estimates, dependencies, risk analysis, and known unknowns. Use when user asks to "estimate", "size", or "analyze complexity" of work items.
43pr-split
Split a branch into a logical sequence of stacked PRs for easier review
27batch-lint-cleanup
Analyze ESLint violations and auto-fix specific rules in isolation
23recall
Load branch context and browse project memory for session resumption
22plunker
Create and manage Plunker (plnkr.co) code examples for AG Charts and AG Grid. Use this skill whenever the user mentions plunker, plnkr, or plunk, wants to create a shareable code demo or bug reproduction, needs to fork or modify an existing plunk, or asks for a live code example they can share via URL. This includes creating repros for JIRA tickets, building demos for stakeholders, downloading plunks to inspect them, or making any interactive code example hosted on plnkr.co. Also trigger when users ask for "a shareable example", "a repro", "a demo I can send", or "a live example" — even without explicitly saying "plunker".
22sync-ag-shared
Sync ag-shared subrepo changes across ag-charts, ag-grid, and ag-studio repos
22