Skip to content
This repository has been archived by the owner on Dec 29, 2023. It is now read-only.

Handle pre-release & metadata in version numbering #26

Open
ethanjli opened this issue Mar 30, 2021 · 0 comments
Open

Handle pre-release & metadata in version numbering #26

ethanjli opened this issue Mar 30, 2021 · 0 comments
Labels
domain: repo On the repository itself type: fix Iterations on existing features or infrastructure work: complicated The situation is complicated (known unknowns), good practices used

Comments

@ethanjli
Copy link
Member

ethanjli commented Mar 30, 2021

We will want to be able to add a pre-release string (e.g. 1.0.0-alpha.1) to our version numbers, and for this to be appropriately handled by the Github Actions workflows. Similarly, we may want to modify our build file naming to make metadata (e.g. build date and/or BOM variant) into the semantic versioning specifications for build metadata. I'd prefer to keep the build date up from the end of the filename, though - so that builds of the same version from different days are kept together by filename sorting.

@ethanjli ethanjli added type: fix Iterations on existing features or infrastructure work: complicated The situation is complicated (known unknowns), good practices used domain: repo On the repository itself labels Mar 30, 2021
@ethanjli ethanjli added this to the ODSv1.0.0-PP-T41v1.0.0 milestone Mar 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
domain: repo On the repository itself type: fix Iterations on existing features or infrastructure work: complicated The situation is complicated (known unknowns), good practices used
Projects
None yet
Development

No branches or pull requests

1 participant