Skip to content
RhodeCode
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.

ShippedIn buildPlannedConsidering

    support@rhodecode.com

    Tell us what RhodeCode should do and the problem behind it. The form opens an email in your mail app, so you see exactly what is sent and replies come straight back to you.

    Edition
    Version control

    Prefer to discuss it in public? Post it on the community portal ↗

    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