Hi, I would at least support the current and the previous Eclipse releases (Juno + Kepler). This would be in line with the strategy from the Eclipse Automotive Industry Working Group. Unless it requires too much effort, we can continue supporting older releases as well.
I vote for keeping the Juno support. Proposal: maybe we should ask for additional build jobs at Eclipse. One for each Eclipse release. regards Mark -- Mark Brörkens Softwarearchitekt, Projekt- und Produktmanager Telefon: +49 30 69 535 878 Telefax: +49 30 62 908 067 Mobil: +49 151 61301259 (bevorzugt) http://www.itemis.de mark.broerk...@itemis.de http://xing.to/mark_broerkens http://twitter.com/MarkBroerkens itemis AG Mulackstraße 22 10119 Berlin Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus Am 21.10.2013 um 10:35 schrieb Michael Jastram <mich...@jastram.de>: > Howdy, > > We currently support and maintain three target definitions: Indigo, Juno and > Kepler. I propose to stop supporting Juno, so that we only support one 3.x > and one 4.x based version. If you object, please let me know by the end of > the day. > > Thanks, > > - Michael > > -- > Dr. Michael Jastram +49 (162) 274 83 94 http://jastram.de > Geschäftsführer Formal Mind GmbH http://formalmind.com > Vorsitzender rheinjug e.V. http://rheinjug.de > Project Lead Eclipse Requirements Modeling Framework http://eclipse.org/rmf > _______________________________________________ > rmf-dev mailing list > rmf-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/rmf-dev
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/rmf-dev
