> We could open each of the 105 issues and change the "fix for" version > so something like "cas4api". It's a lot less work to simply close > them out in batch and start with a fresh version number "5.0".
Why are we wasting any energy on issues that target a version/branch that we've agreed is a dead end, at least for the foreseeable future? >> This way, we keep JIRA history (for the original 4.0 renamed as 3.9.EXP) and >> can create new 4.0.x version names in JIRA. > > This doesn't by us much other than preserving the "4.0" number...and > version numbers are cheap! :) Disagree. We worked hard on the current roadmap proposal with clear justification for the 4.0 numbering and I'm loath to change it for bookkeeping reasons in Jira. Your solution and Jérôme's are effectively the same, but with different version numbers. Let's just choose a suitable version name/number that doesn't require a bump, change the target version in batch, then close them. > Adopt "5.0" has the next near term major release -1 M -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
