Skip to content

Milestones

List view

  • Due by July 31, 2025
    2/2 issues closed
  • Due by August 31, 2025
  • Due by June 30, 2025
    10/10 issues closed
  • Due by April 25, 2025
  • Due by March 31, 2025
    2/2 issues closed
  • Main features: - Alter inverted index - Logging DSL - Remove rustpython(#5060)

    Due by February 14, 2025
    17/18 issues closed
  • Due by December 10, 2024
    11/11 issues closed
  • Main features: - Auto Rebalance Regions - Smart Index

    Due by June 30, 2024
    3/3 issues closed
  • Main features: - [GreptimeFlow](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2024-01-17-dataflow-framework.md) - Drop Database

    Due by April 30, 2024
    22/24 issues closed
  • Main features: - [Region Migration](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-11-07-region-migration.md) - [Inverted Index](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-11-03-inverted-index.md) - [Metrics Engine](https://github.com/GreptimeTeam/greptimedb/blob/main/docs/rfcs/2023-07-10-metric-engine.md)

    Due by March 1, 2024
    18/18 issues closed
  • Due by January 5, 2024
    7/7 issues closed
  • No due date
    11/11 issues closed
  • Due by September 30, 2023
    58/58 issues closed
  • Due by February 15, 2023
    39/39 issues closed
  • Improve distributed mode, enhance fault tolerance.

    Due by March 31, 2023
    15/15 issues closed
  • GreptimeDB set off in April 2022 and had just open-sourced on Nov. 15th, 2022. Many of our ideas are still on their way, yet to be polished. As we work towards GreptimeDB 2023, it's natural to ask what's next. This roadmap presents goals our team is working on and concepts we have for our shared community. * To give people a sense of what to expect in GreptimeDB over the next 6 months; * for those who would like to contribute to GreptimeDB at GitHub, to help provide "starting points" for how to get involved, and a sense of what kind of projects we are looking for. We will focus on three sections: * Distributed solution at the production level * Deeply optimize storage and query engine * Compatible with open protocols

    Due by July 1, 2023
    32/33 issues closed
  • Our first alpha release.

    Due by August 5, 2022
    10/10 issues closed