James, If uPortal adopts Semantic Versioning, it will do so for the uPortal 4.2 release (or, I suppose, for some later release). I wouldn't expect it to affect the versioning policy for, and I haven't proposed that it be applied to, uPortal 4.1.
Therefore, the rules for whether https://github.com/Jasig/uPortal/pull/384 (a change to how auto-suggest works) would merge to 4.1-patches or not are the traditional rules documented at https://wiki.jasig.org/display/UPC/Release+Strategy . The release strategy documented there is roughly in terms of pain, with patch releases (4.1.1 to 4.1.2, say) being "painless". (A Semantic Versioning release strategy would say that that pull 384 doesn't merge to 4.1-patches because it is not a bug fix, regardless of its backwards-compatible-ness). Skimming #384, I'd be concerned that it doesn't belong in 4.1-patches even under the current release strategy. It removes autosuggest_handler.jsp outright - did adopters expect they could modify autosuggest_handler.jsp as part of the exposed "API" of uPortal such that they will experience greater than zero pain on that JSP's removal? That said, I'm not that concerned - I'm pretty sure Wisconsin isn't using that autosuggest solution anyway. JW> I won't need to back-merge the changes if we will be doing minor releases much more frequently; Semantic Versioning doesn't in itself have anything to say about release frequency. Personally, I would favor a uPortal 4.2 sooner rather than later, and functionally focused on retiring org.jasig.portal.security code in favor of switching to Spring Security. And on starting to do Semantic Versioning. :) So, perhaps it's a separate question, of how soon the project envisions cutting a 4.2 release. JW> I plan to wait until after you release 4.1.1 before merging to rel-4-1-patches. Appreciated. Andrew From: James Wennmacher <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, August 19, 2014 at 3:03 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: [uportal-dev] uPortal semantic version #s I know there were some discussions RE semantic versioning. I was wondering where we were at with that. I just merged a feature enhancement into master ( https://github.com/Jasig/uPortal/pull/384). I'm debating whether to merge it into rel-4-1-patches, in part because I had added it to the uPortal 4.1 manual some time ago (core feature is in 4.1.0). I won't need to back-merge the changes if we will be doing minor releases much more frequently; e.g. releasing a 4.2.0 soon, though that also gets into the issue of documentation ... I don't think we want to create a uPortal 4.2 manual right away though (I like Andrew P's suggestion to move the manual into git with the project if we do go to semantic versioning). @Andrew P: I plan to wait until after you release 4.1.1 before merging to rel-4-1-patches. Thanks, -- James Wennmacher - Unicon 480.558.2420 -- You are currently subscribed to [email protected]<mailto:[email protected]> as: [email protected]<mailto:[email protected]> To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
