Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Status and Outlook for Luna M1

Ok, it's Thursday morning :)

Only a few more have been enabled, but that includes DTP and BIRT, so that should help Luna (Kepler RC1 repo is already considered done).

That allowed me to enabled the "JPA" portions of WTP (since depends on DataTools) which, I noticed, some others depended on,
but I had to leave WTPs "JPA Diagram Editor" disabled, since it depends on Graphiti, which is not enabled yet.

Which brings me to my main point. Scanning the list of 22 disabled contributions, I'd guess about half are "leaf" components, so if you don't get enabled, it'd hurt no one but your self ... and maybe community and adopters? But, I'd guess, the other half such as "graphiti", "gmf"? a few emf ones? and DLTK are definitely "building blocks" that need to be enabled or else others downstream can not function or be enabled. If you are a "consuming" project and need some of those lower level ones enabled, I'd encourage a lot of "project-to-project" communication so they know how much you depend on them, and the effect they have by being "late" or incomplete, etc.

So, I'm just asking everyone to be aware of your place in the eco system and plan accordingly. I suspect I'm just stating the obvious ... but not sure what else I can do to help.


= = = = = = = = =

actf.b3aggrcon -
amalgam.b3aggrcon -
amp.b3aggrcon -
dltk.b3aggrcon -
ecf.b3aggrcon -
emf-compare.b3aggrcon -
emft-ecoretools.b3aggrcon -
emft-eef.b3aggrcon -
emft-egf.b3aggrcon -
gmp-gmf-tooling.b3aggrcon -
gmp-graphiti.b3aggrcon -
jwt.b3aggrcon -
koneki.b3aggrcon -
m2m-atl.b3aggrcon -
m2t-acceleo.b3aggrcon -
mdt-modisco.b3aggrcon -
mft.b3aggrcon -
mylyn-docs-intent.b3aggrcon -
pdt.b3aggrcon -
soa-bpel.b3aggrcon -
soa-sca.b3aggrcon -
windowbuilder.b3aggrcon -

Back to the top