Darknet: Move to release version tags in vMAJOR.MINOR.PATCH format?

[ianshmean]

@AlexeyAB The work that's been put into this fork is fantastic, and very much appreciated. One thing that would be great would be to start using release tags that are a little more traceable than the current style.

Would it be possible to move to vMAJOR.MINOR.PATCH format? perhaps major would now be 3, to align with YOLOv3 and it looks like there have been two minor releases since, so the current version would be 3.1.0?

Just a suggestion that I think would help adoption

[AlexeyAB]

@ianshmean Hi,

Yes, I will think about it.
also versions must match in source code

• https://github.com/AlexeyAB/darknet/blob/1cd332e4cac001ffcc12a24c72640fe02b69a8a0/src/parser.c#L1038-L1040
• https://github.com/AlexeyAB/darknet/blob/1cd332e4cac001ffcc12a24c72640fe02b69a8a0/src/parser.c#L1236-L1253
  with Cmakelist https://github.com/AlexeyAB/darknet/blob/1cd332e4cac001ffcc12a24c72640fe02b69a8a0/CMakeLists.txt#L3-L6

[ianshmean]

@AlexeyAB Given the significant number of improvements & fixes since the last release, it would be great to release a new version, in the format mentioned above. It would make referencing use of this codebase a lot simpler/clearer

[omaralvarez]

This would be great, coupled with git tags and github releases. I'm working on creating a conan recipe for darknet, and right now not having versions is a problem (https://github.com/omaralvarez/conan-darknet).

[ianshmean]

I just wanted to check on the status of this? I'm about to version and release a package that is dependent on this, and currently there is no decent way to link the versioning clearly (currently using git hashes, which aren't easily meaningful).

I can wait to release if a semver-tagged release is imminent (given this is marked as "in progress")?