search

eclipse-velocitas / velocitas-docs

Documentation artifacts of Velocitas
https://eclipse.dev/velocitas
Apache License 2.0
9 stars 6 forks source link

Eclipse Velocitas Release Strategy Proposal #88

Closed kse3hi closed 1 year ago

kse3hi commented 1 year ago

Motivation:

As developers/users of Eclipse Velocitas, we would like to have clear vision of release strategy, with clear overview of released components (incl. their versions). It will be great to have stable and baselined state of template and major components to be able to keep stable environment especially in dynamical development phase.

Versioning Principle

Major releases include API changes (potential for downstream breakage); Minor releases add new functionality, but are API compatible with previous versions; and Service releases include bug fixes only and include no significant new functionality.

Versioning scheme: <major>.<minor>.<service> Example: 0.1.0

Release Strategy Proposal:

image

kse3hi commented 1 year ago

Communication threat on GitHub about template versioning, that can help us with our Versioning Strategy: https://github.com/orgs/community/discussions/45248

Related feature on CLI side: https://github.com/eclipse-velocitas/cli/issues/65

gkreyssing commented 1 year ago

@kse3hi As we release velocitas, I would close this issue. Do you agree?

kse3hi commented 1 year ago

@gkreyssing , release concept was accepted and implemented.