Since the next release of RAD will be the "commissioning" build, it is worth considering bumping the major version of all the schemas. This provides us a couple of advantages.
- It draws a nice distinction between what is flight data and what is pre-flight data, programmatically we can leverage this necessary.
- It makes it relatively easy for someone manually examining a data product to determine if the data is pre-flight aro flight data because one can simply look at the extension version/tag versions in the ASDF file.
- This can make debugging data files a little simpler especially during the transition where pre flight and flight data are being mixed.
We should also make the commissioning build the 1.0.0 release of RAD (and RDM).
Note that this is not technically a "semantic versioning change" but realistically every schema change is a major change since pretty much all of them are not fully backwards compatible due to the fact that you can structure any undefined key however you want. As a result we have been bumping the "minor" version with every schema change. It makes sense to use the major version to indicate something useful.
In addition to this bump we should also discuss under what additional conditions we may want to bump the major schema version. For example we may wish to do another major bump at the end of commissioning or when something drastically changes in the mission itself.
Since the next release of RAD will be the "commissioning" build, it is worth considering bumping the major version of all the schemas. This provides us a couple of advantages.
We should also make the commissioning build the 1.0.0 release of RAD (and RDM).
Note that this is not technically a "semantic versioning change" but realistically every schema change is a major change since pretty much all of them are not fully backwards compatible due to the fact that you can structure any undefined key however you want. As a result we have been bumping the "minor" version with every schema change. It makes sense to use the major version to indicate something useful.
In addition to this bump we should also discuss under what additional conditions we may want to bump the major schema version. For example we may wish to do another major bump at the end of commissioning or when something drastically changes in the mission itself.