Skip to content

graduating API to beta #888

Open
Open
@errordeveloper

Description

@errordeveloper

Right now our config file schema (aka the API), is at v1alpha5. It would be reasonable that we promote it to beta soon, as long as we have the following.

  • backwards/forward compatibly guarantees defined clearly
  • some form of feature deprecation policy
  • all commands have support for --config-file flag
  • schema migration

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/config-filearea/tech-debtLeftover improvements in code, testing and buildingkind/breakingkind/featureNew feature or requestpriority/backlogNot staffed at the moment. Help wanted.priority/important-longtermImportant over the long term, but may not be currently staffed and/or may require multiple releases

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions