... at least I want to make an attempt to get an agreement.
a) Use git flow release
b) Versioning convention, I propose typical 3 level versioning vXX.YY.ZZ where...
b-1) Increment ZZ for completely backward-compatible release
b-2) Increment YY for partially backward-compatible module, defined as backward incompatibility outside "core" directory (so a change in module configuration format, caffe interface, etc)
b-3) Increment XX for backward incompatible change in "core"
... at least I want to make an attempt to get an agreement.
a) Use git flow release b) Versioning convention, I propose typical 3 level versioning vXX.YY.ZZ where... b-1) Increment ZZ for completely backward-compatible release b-2) Increment YY for partially backward-compatible module, defined as backward incompatibility outside "core" directory (so a change in module configuration format, caffe interface, etc) b-3) Increment XX for backward incompatible change in "core"
The current (initial) motivation is to push out the current develop https://github.com/LArbys/LArCV/commit/29ea5ed78475c6656c9f68410962cb10d1ecb6aa that is still backward compatible with the caffe configuration used for long by now.