|Re: [cross-project-issues-dev] Capabilities Galileo Requirement|
Galileo M6 marks the deadline for completing the "Capabilities" requirement:
I'm wondering if anybody has implemented this req already or spent any thought on it.
Any pointers are welcome. IMO Defining the actual work of defining the Capabilities is not a big deal, just adding a feature, a bundle, a plugin.xml - that should be it. The problem is more in finding out WHAT we want to see on the train...
- I think it would be useful if the "Separate Feature including the exemplary Capability Defs" followed some common naming scheme across all projects.
- Any common guidelines, e.g. are we disabling entire perspectives?
- Are we enlisting the Capabilitiy features on the Galileo site, i.e. should they be part of the build model?
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
cross-project-issues-dev mailing list
Back to the top