> 1) Release 2.1.6 and mark it in JIRA as the EOL (no entry for 2.1.7). Or,
Not so sure about this... You can never know if not somebody jumps up and provides two critical bug-fixes for 2.1.x because he needs it. On the other side: is there really and possibility that this happens? If we remove 2.1.7 we'll make a clear statement: don't bother us with those stone-age-versions and move on... > 2) Leave it open in JIRA, and mark the version in JIRA as EOL, not to > be released. Do we want to release this if there is a single bug-fix here? I'm sure that we wont receive any more than at max 1 in half a year? OK, after writing my thoughts down I'm definitely for option 1 :) > > Regardless of which choice we opt for, I think that we should > de-allocate the jenkins profile as we're not actively developing the > branch (https://builds.apache.org/job/Karaf-2.1.x/). We'll of course > create new profile for 3.0.x and 3.1.x once those branches are > available. Nothing to add; +1 Kind regards, Andreas > > Cheers, > Jamie >
