nothing else to say, Mike did a nice sum-up on it :-) +1 for option one +1 for de-allocating the Jenkins profile
regards, Achim Am 12.07.2011 21:13, schrieb mikevan: > +1 to option one. That said, is anything ever really EOL? The reality is > that if someone discovers a critical bug that keeps 2.1.7 from working, > we'll have a hard time saying "Upgrade and go away". Its EOL, but with > limitations forced by reality. > > +1 to de-allocating the Jenkins profile. > > > Andreas Pieber wrote: >>> 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 >>> > > ----- > Mike Van > -- > View this message in context: > http://karaf.922171.n3.nabble.com/DISCUSS-Karaf-2-1-x-end-of-life-tp3163463p3163582.html > Sent from the Karaf - Dev mailing list archive at Nabble.com. -- ----- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
