[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Thank for the info Florian... I'm switching to the mailing list to follow
this discussion.
- Related to the JWT bug Tracker:
Seems like bugs and features requests are handled the same way inside JWT
(same tool) Could you confirm that ?
- I would like to make a proposal related to the JWT roadmap:
0.6 release is intended to be the one used by "vendors" as a basis for
customization. I would suggest to release the 0.6 version as planed (aspects
related work) and to schedule another release (0.7 ?) which will be the one
called "for vendors". This one would include, among other developments, the
requirements coming from Bull as well as any other requirement which will
allow BPM vendors to build tools on top of JWT.
What do you think ?
Regards,
Miguel Valdes
BPM Manager
Bull, Architect of an Open World TM
1, rue de Provence
38130 Echirolles (France)
Direct Line: +33-4-76-29-72-28
*Orchestra*, The BPEL open source project: http://orchestra.ow2.org
*Bonita*, The XPDL open source project: http://bonita.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.
-----Message d'origine-----
De : Florian Lautenbacher
[mailto:florian.lautenbacher@xxxxxxxxxxxxxxxxxxxxxxxxxx]
Envoyé : mardi 25 novembre 2008 13:27
À : 'Miguel Valdes Faura'; 'Marc Dutoo'; 'Koen Aers'
Cc : 'Tom Baeyens'; 'Tom Baeyens'; 'Christian Saad'; 'Mickael Istria';
pierre.vigneras@xxxxxxxx; 'John Graham'
Objet : AW: JWT - jBPM - Bull meeting 20081121 - notes
Hi Miguel,
>>Marc, I remember in your slides, you proposed a tentative roadmap for next
JWT releases. As Florian mentioned yesterday, this roadmap should be
probably updated to match with Galileo milestones so I would like to
participate (If you let me :-) on the definition of the roadmap.
Sure, any support is welcome here as well. For the moment we defined our
project plan which can be seen in [1]. There, the next release has been
planned for mid December which shall include all the aspect concerns. In mid
February the following release (0.7) has been scheduled including
improvements for the aspects as well as SCOrWare related topics special to
SOA. The "final" release (currently named 1.0, but I'm not sure whether this
will already be a graduation from Incubation phase) is scheduled for the end
of June ("JWT for Users"). I guess that we will more likely have the Galileo
release and sometime after that the graduation release.
So your plans for your releases (Bull and JBoss) will be considered when
adapting the project plan. However, we probably need also to make sure to be
mostly in line with the Galileo milestones which would be the following
(visible in the calendar on [2]):
There should be a M3+0 in the beginning of November ("was" our 0.5 release)
M4+0 on the 12th of December (might be our 0.6 release, but more likely we
will need an offset and stay with M4+1 (17th, or M4+2 29th of December).
M5+0 is scheduled for 30th of January 2009 (M5+1 3rd February, M5+2 6th
February)
M6+0 on 13th of March (one of these could be our 0.7 release).
As I understood a project does not need to have new features in each
milestone of Galileo, is that correct? Only it needs to make sure that at
each point of time a milestone is released, the project is buildable?
Concerning the following discussions: since we are all interested on the
project and probably no more confidential things will be exchanged, would it
be okay for the future to use the jwt-dev-mailing list again (hopefully
everyone in this conversation already registered for it)? This makes it a
lot easier not to forget anyone... :-)
Best regards,
Florian
[1]
http://www.eclipse.org/projects/project-plan.php?projectid=technology.jwt
[2] http://wiki.eclipse.org/Galileo_Simultaneous_Release
