Hi everyone, As mentioned during yesterday's meeting, the versioning strategy for new/infrequently released components needs discussion/finalization.
Components such as NEXUS and ingester are updated frequently enough that this isn't an issue for them. However, nexusproto and potentially new components such as insitu data services pose a potential problem. The simple solution would be to version each updated component to match the SDAP release version. For example, nexusproto's latest released version is 1.0.0. Should it be updated in 1.3.0 (which is almost certain), it's version will go from 1.0.0 to 1.3.0. The issue with this is, when new components are released, they will be versioned as mature code. On the other hand, not using a strategy like this would require us to keep track of all the differing versions of our various components each release cycle. Perhaps we could adopt a hybrid approach, with new components having versions like 0.x.x until we deem them mature enough to "catch up" with the rest of the components. I'd like to open this to discussion so maybe we can work out a formal method and put it to a vote. (Is there a process for voting for one of a set of choices, or is it just yes/no?) - Riley
