Skip to content

Comet 1.0.0 Release #4082

Closed
Closed

Description

@andygrove

What is the problem the feature request solves?

I would like to start planning ahead for a 1.0.0 release. Let's use this issue to discuss what that means.

Current planned items:

  • Demonstrated cost savings for TPC-H and TPC-DS at SF1000 (1TB)
  • Consistent logging
  • Thorough documentation for compatibility status
  • Review all configuration options and consider renaming some for consistency
  • Documented policy for how long we will support Spark versions
  • Documented process for preventing major performance regressions
  • Documented process for versioning (semver) moving forward. What does that mean for Comet?

Nice to have:

Correctness and critical-priority issues to resolve before 1.0.0

Open issues labeled correctness and/or priority:critical. Items marked 🔴 are also priority:critical. (Generated 2026-07-07)

Describe the potential solution

No response

Additional context

No response

Activity

  1. added this to the 1.0.0 milestone on Apr 25, 2026
  2. parthchandra commented on Jul 6, 2026

    @parthchandra
    Contributor

    I'd like to see iceberg metadata columns support make it #4082 (depends on a bunch of PRs in iceberg-rust though).

  3. mbutrovich commented on Jul 6, 2026

    @mbutrovich
    Contributor

    I will get Iceberg 1.11 support into shape #4840.

  4. andygrove commented on Jul 28, 2026

    @andygrove
    MemberAuthor

    We plan on cutting the 1.0.0 release candidate this Friday, 7/31

  5. andygrove commented on Jul 29, 2026

    @andygrove
    MemberAuthor

    I would like to backport #5079 to increase TPC-DS coverage

  6. andygrove commented on Jul 29, 2026

    @andygrove
    MemberAuthor

    I would also like to back port #5110

  7. andygrove commented on Jul 29, 2026

    @andygrove
    MemberAuthor

    another one #5132

  8. andygrove commented on Jul 31, 2026

    @andygrove
    MemberAuthor

    We need a few more days for the release. I'm going to stop back porting PRs to branch-1.0 and will do hard reset on main branch next week and then create fresh PRs to bump version, add changeling, etc.

    Goal is to have the release candidate available by Friday 8/7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions