Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
ctrueden opened this Issue May 1, 2014 · 2 comments

Comments

Projects
None yet
1 participant
@ctrueden
Copy link
Member

commented May 1, 2014

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

This comment has been minimized.

Copy link
Member Author

commented May 1, 2014

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

This comment has been minimized.

Copy link
Member Author

commented Oct 11, 2018

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.

@ctrueden ctrueden closed this Oct 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.