Public roadmap
Release train · 5.14 → 5.16+
Published, because an open core has to be checkable.
Two lanes, four release lines. Community items are driven by community choices; the enterprise programme influences the rest through roadmap surveys. Dates are intentions — we would rather ship late than pre-announce.
Lane
5.14
Shipped
current release
5.15
In build
next release
5.16
Planned
following release
5.16+
Considering
no date committed
CE
Community
ShippedIn buildPlannedConsidering
02Governance
How an item gets onto this board
Community Edition priorities come from the community; Enterprise priorities come from the customers who fund them. Neither lane is decided by marketing.
02.1
Community proposal
Anyone can open a feature request on the community portal. Discussion is public and so is the outcome.
community.rhodecode.com
02.2
Enterprise survey
Licensed customers rank candidate work twice a year. Weighting follows seat count, not deal size.
Twice yearly
02.3
Committed to a line
An item only gets a release number when the work is scoped and someone owns it.
No date without an owner
02.4
Shipped or moved
If it slips we move it and say so on this board rather than quietly dropping it.
Slippage is published
03Track record
What actually shipped
A roadmap is only credible against a record. Every release since 2010 has published notes, and none of these dates moved after the fact.
- 5.11Path permissions in MercurialPath-level grants inside hg repositories, matching Git and Subversion. (opens in a new tab)
- 5.1Celery hooks subsystemRewritten hook execution and an SVN event refactor for Docker deployments. (opens in a new tab)
- 5.0Python 3.11 and RCstackContainerised installation only, with substantial performance work throughout. (opens in a new tab)
- 4.xArtifact store and gistsBinary artifacts and snippets under the same permission model as source. (opens in a new tab)
- 2010First public releaseRhodeCode 1.6.0, then a Mercurial repository manager, released as open source. (opens in a new tab)