Skip to content

Exposition format: Versioning #545

Open

Description

@beorn7

We are still stuck with v0.0.4. With maturing the exposition format, we should bump the version to utlimately 1.0.0. Also, we need to figure out how to document older versions, and what requirements we have for support of various versions by implementers.

Activity

  1. beorn7 commented on Sep 9, 2016

    @beorn7
    ContributorAuthor

    We should also get clarity where and how to advertise/mark the version, cf. prometheus/common#34

  2. brian-brazil commented on Sep 10, 2016

    @brian-brazil
    Contributor

    The way I'm thinking is that a 1.0.0 parser would also handle 0.0.4 output, with no more than minor mangling (e.g. the comment escaping). The only real problem with that is if we introduce the end marker.

  3. grobie commented on Sep 10, 2016

    @grobie
    Member

    On a different note, it'd be helpful to include information about Prometheus in the Content-Type header value. text/plain; version=0.0.4 doesn't help to identify the format definition if someone doesn't know about Prometheus.

  4. RichiH commented on Sep 11, 2016

    @RichiH
    Member
  5. hdost commented on Feb 3, 2022

    @hdost
    Contributor
  6. lasomethingsomething commented on Nov 18, 2026

    @lasomethingsomething

    @jan--f Any reason not to close?

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions