| RE: [jwt-dev] Galileo requirements |
|
Hi Florian, Those are the main topics
to be addressed ASAP. Additionally things like a dedicated Test Plan for JWT
and the creation of an update site to allow Galileo build are also required. If
I well understood, there is also one meeting per month in average to check the activity
progress of projects. My team is interested on
help you (you and Marc) with the milestone offset and the ramp down policy +
with upcoming tasks: test plan, meetings participation, update build… As
you have a better experience than us with Eclipse related technologies I would
suggest somebody of your team or Marc team as engineer for Galileo. Best regards, Miguel BPM Manager Bull,
Architect of an Open World TM *Orchestra*, The BPEL
open source project: http://orchestra.ow2.org This e-mail contains
material that is confidential for the sole use of the intended recipient. Any
review, reliance or distribution by others or forwarding without express
permission is strictly prohibited. If you are not the intended recipient,
please contact the sender and delete all copies. De :
jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] De la part de Florian Lautenbacher Hi all, I found the following requirements for Galileo by now: - on [1] we need to express our wish to be integrated into
Galileo. This includes the project lead(s), responsible release engineer,
milestone offset and ramp down policy. Who will be the responsible release
engineer for Galileo? Marc? This needs to be done by M4+0 (12th of December) - Projects must have a project plan in XML-format (already
done, maybe might be adapted to fit the Galileo schedule, ToDo myself) - Communicate: Somebody must subscribe to the mailing list
cross.project-inbox (I already did) - Attendance: Project representatives must attend the
meetings and conf calls for Galileo; here we should probably divide this work
on several shoulders - Until M6+0 the ramp down policy must be written (13th of
March 2009) - IP must be approved (thats the case with JWT) - Plugins must be resumed by Orbit (such as JDom in our
case) There are several other issues described on [1] concerning
bundles, internationalization, etc. which we need to resolve in the following
month. But I guess the most important thing is to express our wish on the Wiki
page. Are there any things that I am missing? Best regards, Florian |