I think we should ask EMO to give us some guidance regarding minimal
timeline for converting XSL Tools into a project...
EMO,
XSL Tools is a component of the WTP Incubator project. This component is
reaching maturing and we are discussing the various options for how to move
it out of the incubation. One of the options we are discussing is to convert
the component into a project under WTP and then to do a graduation review on
that project. Could you give us some guidance for how long component to
project conversation would take? Would the mandatory wait time between
project proposal and the creation review apply in this case? How backed up
are the admins for making the necessary provisioning changes?
The reason we need to know this information is that we are trying to decide
whether this approach is feasible if the goal is to ship XSL Tools as part
of the main (non-incubating) WTP distributions for Galileo.
- Konstantin
-----Original Message-----
From: wtp-incubator-dev-bounces@xxxxxxxxxxx
[mailto:wtp-incubator-dev-bounces@xxxxxxxxxxx]
On Behalf Of Doug Satchwell
Sent: Friday, February 20, 2009 4:19 AM
To: WTP Incubator Dev list
Subject: Re: [wtp-incubator-dev] More on XSL Graduation ...
As you probably guessed I'm no authority on Eclipse process!
I was mainly alluding to the fact that to have an XML project we
would need
all of the XML code in it, and that means getting the current maintainers
of
the XML related plugins (*.xml, *.xsd and *.dtd) to agree that they will
(eventually) move their code into that project. There is also the question
of who leads the project, as with all that code it ought to have someone
full-time. Its not my day job to lead the XSL Tools project (though I
would
enjoy that - so I'm open to offers ;-), and I don't think Dave spends 100%
of his day on it either (thats right Dave?). These things may take some time
sort out, but I appreciate we don't need to do them immediately.
Now, the first part of Konstantin's plan towards creating a new XML
project
is to make XSL Tools a proper WTP sub-project. I'm fine with that as long as
it does not jeopardise the adoption of the code into the Eclipse 3.5
packages. If it does jeopardise that, then I'd much rather carry on as we
are and just graduate into Source Editing. We can then move the XSL Tools
code into the XML project at the same time as all the XML related plugins
are moved.
My main aim is to ensure that XSL Tools gets into this year's packages,
otherwise its going to be another whole year before XSL Tools sees the light
of day, and that would be a real shame because we've all worked hard to get
to where we are now.
Doug
----- Original Message ----
From: Oisin Hurley <oisin.hurley@xxxxxxxxx>
To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Sent: Friday, 20 February, 2009 10:51:47
Subject: Re: [wtp-incubator-dev] More on XSL Graduation ...
I too think that having an XML Tools project is a good idea. However,
it
would
be really quite a massive >undertaking - it would need to be
discussed as
some
sort of high-level strategic review for Eclipse. I'm not >saying it
can't
be
done, its just going to take a lot of time and careful consideration.
Its
not
going to happen any >time soon.
A strategic review of Eclipse is a big ticket item that could not
be started with the creation of a project that is limited to the
creation of XML Tools.
It's usually the other way around - Eclipse made a stratagic
decision to go after runtimes, ergo it constructed the the
RT project.
I'm strongly in favo[u]r of an XML Tools project as a separate
item. I don't particularly care where it is hosted, but I would like
it to be consumable in a fine-grained manner, and for it to
have it's own delivery lifecycle.
--oh
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.1/1962 - Release Date: 02/20/09
07:26:00
