Write up a public rationale for how and why we changed versioning to release-version coupling

[ctrueden]

We have switched to a versioning scheme based on SemVer, with release versioning coupling between components, each of which lives in its own Git repository.

Write up a blog post (and/or Wiki page and mail to the ''-devel'' lists) to provide a rationale why, and give others a chance to help us avert stupid changes in our workflow.

Migrated-From: http://trac.imagej.net/ticket/1788

[ctrueden]

While this issue is most certainly important, we probably don't have time to write detailed documentation about it until after the June 1 release of ImageJ2. Let's shoot for making this writeup our July blog post for ImageJ!

[ctrueden]

More than four years later... it's release version coupling all around. If anyone still disagrees that release version coupling is the way to go, or finds the imagej.net materials about it insufficient, we can always write more on the wiki about it. But I'm closing this issue.