search

epics-motor / motorSymetrie

EPICS support module for the SYMETRIE positioning hexapods
0 stars 0 forks source link

What Github tag numbering scheme should we use in the future? #7

Open MarkRivers opened 2 years ago

MarkRivers commented 2 years ago

The RELEASE.md files lists the following as the existing release numbers:

Do the final 6 digits in these encode the release date?

This is currently just one Github tag, R1-0 which I applied to the version I received from Symetrie.

The question is what numbering scheme should we use for Github tags going forward? Should we use the prior convention of 5.0.date or R1-1, R1-2, which is more conventional for EPICS modules?

prjemian commented 2 years ago

Semantic Versioning (https://semver.org) is one approach.

JohannLamaury commented 2 years ago

Do the final 6 digits in these encode the release date?

That's correct. Our versioning semantic for releases is composed of MAJOR.MINOR.DATE where DATE is defined as YYMMDD

eddybl commented 1 year ago

I think it makes sense to stick to the method used for other EPICS modules

Speaking of tags: since the R1-0 changes there seems to be quite large changes to the code, can we add a new tag for the updated version?