Hi,
not „the expert“ here obviously, but from my past experience everything beyond M4 needs an exception permission from the planning council. David can trigger
that. Its not super hard to get but if you have a chance to get this fixed in time, its always worthwhile :-). (Especially since the guys from EMFStore are next door from you :-) )
just my 2 cents
christian
Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx]
Im Auftrag von Johannes Faltermeier
Gesendet: Dienstag, 17. Dezember 2013 13:25
An: cross-project-issues-dev@xxxxxxxxxxx
Betreff: [cross-project-issues-dev] EMFStore and ECP intend to start with M5 instead of M4
Hi,
EMFStore (+2) and ECP (+3) stated the intent to join the simultaneous release as first-timers. The plan was to make our first contribution to the aggregation build with M4. However we just faced a problem with EMFStore. ECP is dependent
on EMFStore.
So basically I am wondering if it is possible to make our first contribution to the build directly starting with M5, instead of trying to rush in a fixed version, which will most probably be late for M4 +2. I am not sure if this is officially
allowed however, since it is stated in the wiki that M4 is a deadline. Do we need an exception process or is it ok to start with M5?
--
Johannes Faltermeier
Software Engineer
EclipseSource Munich
Email: jfaltermeier@xxxxxxxxxxxxxxxxx
Web: http://eclipsesource.com/munich
Mobil: +49 178 135 34 62
Phone: +49 89 21 555 301 - 4
Fax: +49 89 21 555 301 - 9
EclipseSource München GmbH
Agnes-Pockels-Bogen 1
80992 München
General Managers: Dr. Jonas Helming, Dr. Maximilian Kögel
Registered Office: Sailerstraße 5, 80809 München, Commercial Register
München, HRB 191789
-------------------------------------------------------------