[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [tools-pmc] RE: [ve-dev] Contribution on VE with XML editor
|
Philippe,
You'll find the the incubating project rules will not allow you to use
parallel IP unless you have a separate project for the incubator.
Ed Merks/Toronto/IBM@IBMCA
mailto: merks@xxxxxxxxxx
905-413-3265 (t/l 969)
"Philippe
Ombredanne"
<pombredanne@gmai To
l.com> "'Nick Boldt'"
Sent by: <nickboldt@xxxxxxxxx>, "'Tools PMC
tools-pmc-bounces mailing list'"
@eclipse.org <tools-pmc@xxxxxxxxxxx>
cc
10/21/2007 02:18 Subject
PM RE: [tools-pmc] RE: [ve-dev]
Contribution on VE with XML editor
Please respond to
pombredanne@gmail
.com; Please
respond to
Tools PMC mailing
list
<tools-pmc@eclips
e.org>
Nick Boldt wrote:
>Please forgive the naivete' of this question, but why can't pieces of
incubating code live in the same repo as stable code?
>Could you not just label the incubating bits with "Incubation" in their
feature.xml/manifest.mf files,
>in adherence to the incubation rules, and package those features in a
separate zip from the main
>VE SDK/runtime zips, named too with "incubation" in the zip name, eg.,
ve-unstable-incubation-I20071021.zip ?
>Why do we even need a separate project or component? Surely the addition
of
new API or tools to an
>existing project or component can be done in that project or component,
especially if the new bits are
>versioned appropriately with a 0.x.0 number instead of the higher #
associated with the previously-released stable stuff ?
I like that . This is even simpler, and brilliant!
--
Cheers
Philippe
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
