<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Curtis,<div><br></div><div>I would prefer SemVer, but mainly because this seems closer to the way its currently done and I’m getting used to that way. So really no strong opinion at all.</div><div><br></div><div>What would be nice would be some kind of notification when new pom parents are released. When revisiting some projects I haven’t been working on for a while, I often find myself checking <a href="http://maven.imagej.net">maven.imagej.net</a> to find out, eg, what the latest pom-fiji version is, so that I can use the latest and greatest as a parent. Is there already some mailing-list or similar in place that sends such release notifications?</div><div><br></div><div>best regards,</div><div>Tobias</div><div><br><div><div><div>On 17 Nov 2014, at 20:39, Curtis Rueden <<a href="mailto:ctrueden@wisc.edu">ctrueden@wisc.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi everyone,<div><br></div><div>This is a question for anyone consuming the pom-* parents of the SciJava software stack.</div><div><br></div><div>We want to start versioning these POM parents according to consistent rules. (Unfortunately, right now, the approach is vague and potentially inconsistent [1].) We came up with the following two possible schemes, and would like your feedback on which one you would prefer.</div><div><br></div><div>== 1) SemVer ==</div><div><br></div><div>Every POM parent has three digits, X.Y.Z.</div><div><br></div><div>The X digit is "major" and when incremented indicates a breaking change of some sort: either A) plugin config changes requiring downstream changes, or more commonly B) major SemVer dependency version bumps (e.g., managed scijava-common version updated from 2.35.0 to 3.0.0). This would exclude 0.x and beta components though (so e.g. imglib2-realtransform could go from 2.0.0-beta-27 to 2.0.0-beta-28 without bumping pom-imglib2's X digit).</div><div><br></div><div>The Y digit is "minor" and incremented when dependency versions change in a SemVer-compatible manner, or when plugin configuration is added or improved.<br></div><div><br></div><div>For critical bug-fixes where a given POM parent is somehow compromised or broken, the third digit Z can be bumped before going to the next Y. (See e.g. the recent pom-fiji 5.0.Z series of releases.)</div><div><br></div><div>== 2) Bread crumb version trail ==</div><div><br></div><div>The pom-scijava parent would have a single version digit. The pom-imagej (which is the next POM down) would have two: the first in lockstep with its pom-scijava parent, and the second being its dedicated version digit. POMs which extend pom-imagej (i.e.: pom-scifio, pom-imglib2 and pom-fiji) would have three digits: the first two in lockstep with pom-imagej and the third their own. And so on down the line—e.g., pom-trakem2 would need four digits: the first three matching the pom-fiji parent and the fourth its own.</div><div><br></div><div>== Pros and cons ==</div><div><br></div><div>Option 1:</div><div>[PRO] Semantic meaning. You can reason whether a given POM is somehow "breaking".</div><div>[PRO] Succinctness. Every parent POM has at most three digits at any one time.</div><div>[CON] Lack of provenance. Not obvious which parent POMs go together without leaning on a tool.</div><div><br></div><div>Option 2:</div><div>[PRO] Clear provenance. You can trivially derive the chain of parent POM versions.</div><div>[CON] Lack of semantics. Harder to tell which POM parent releases might break backwards compatibility.</div><div>[CON] Aesthetics. More than 3 digits in a version string may not be desirable.</div><div><br></div><div>Note that either way, we are in the process of creating a scijava-maven-plugin goal to dump all the component version properties associated with a given parent POM.</div><div><br></div><div>Since either scheme is consistent and useful, we want to institute whichever scheme will annoy everyone less. ;-) So which do people like better: SemVer or breadcrumbs?</div><div><br></div><div>Thanks,</div><div>Curtis<br></div><div><br></div><div>[1] The 5.x POM versioning approach was an attempt to achieve _both_ options above, but Mark & I realized today that the two goals are rather mutually exclusive. That is, we cannot keep POM parent versions fully in lockstep while also maintaining a SemVer versioning scheme.</div></div><div><br class="webkit-block-placeholder"></div>
-- <br>
You received this message because you are subscribed to the Google Groups "scijava" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:scijava+unsubscribe@googlegroups.com">scijava+unsubscribe@googlegroups.com</a>.<br>
For more options, visit <a href="https://groups.google.com/d/optout">https://groups.google.com/d/optout</a>.<br>
</blockquote></div><br></div></div></body></html>