Skip to content

Releases: libuconf/cni

v0.1.0

20 Mar 20:42
Compare
Choose a tag to compare

The first versioned release of CNI!
Things that will happen from now on:

  • Implementations should support a specific version, mentioning it in their README.
    IMPLEMENTATIONS.md will become segmented based on versions.
    Each version will include information re: what various compliance levels/options are.
  • All changes to the format will now go through the issue tracker.
  • The format should never change so much as to become unrecognizable, only details will change.
    If I want to make a way different format, it will not be called "CNI".
    It could be CNI_2, but this is similarly unlikely.

Versions are based on the format (not the reference implementation), i.e the tests.
They have the following meanings:

  • A major version bump signifies something incompatible happening,
    i.e a change that breaks existing tests.
  • A minor version bump signifies changes in behavior that are not major.
    For example, adding a new test that would not pass before the changes.
  • A patch version bump signifies adding or removing a test, without changes in behavior.

Due to the significance of minor and major bumps, development for their features will happen in named branches.
Updates to the documents (SPEC, IMPLEMENTATIONS, README).md may happen on the main branch.