|Re: [cross-project-issues-dev] m2e joining the indigo train|
> With the following note, I'm notifying you that the newly
> reinvigorated m2e project would like to join the Indigo release train ...
Welcome aboard. Remember the official way to declare intent is to mark the "simultaneousrelease" flag in the Foundation's Portal metadata.
> ... as well as the "Eclipse IDE for Java Developers".
EPP package content is technically, formally up to the "package maintainer"; though I'm sure there'd be interest and desirability (though I don't know much about that project). I suggest you open a bug in EPP (I guess under Java Package Component, if you mean it that specifically). There, the pros and cons could be discussed, decisions documented, and (eventually) the details needed to accomplish it (such as feature IDs to pull from common repo).
> When it comes to Indigo compliance, I would like to know if all the
> MUSTs have to be met for the first time you board the train (for us
> in M4), or if they just have to be met by the time the train leave
> the station (in June).
Some have specific milestone deadlines as part of the requirement, but if not otherwise stated, then it means "by the release" (which, if you want to be precise, should be interpreted as meaning by the first release candidate).
Thanks for the questions.
Pascal Rapicault ---11/13/2010 10:12:02 AM---Hi, With the following note, I'm notifying you that the newly reinvigorated m2e project would like
From: Pascal Rapicault <pascal@xxxxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: technology-pmc@xxxxxxxxxxx, eclipse.org-planning-council@xxxxxxxxxxx, Eclipse Packaging Project <epp-dev@xxxxxxxxxxx>
Date: 11/13/2010 10:12 AM
Subject: [cross-project-issues-dev] m2e joining the indigo train
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Back to the top