Skip to content

Define first release artifacts and branches #118

@kimwnasptd

Description

@kimwnasptd

Before creating the first release for this repo, we need to ensure that we are aligned on a couple of details that can affect future releases as well.

Specifically, before the first release we'll need to make sure we've agreed on:

  1. What image names should we use for the migrated components?
  2. What branching strategy should we use for cutting releases?
  3. Which docker tag should we use for the first release?

The above will be quite important to agree on before the release, as it will dictate the future releases as well.

cc @juliusvonkohout @thesuperzapper

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions