Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cft-dev] Fwd: [Bug 489467] Adding CFT to a category in org.eclipse.simrel.build

Hey Nierah, Hey Elson,

can you take care of this?

Thanks!
-Martin



> Anfang der weitergeleiteten Nachricht:
> 
> Von: bugzilla-daemon@xxxxxxxxxxx
> Betreff: [Bug 489467] Adding CFT to a category in org.eclipse.simrel.build
> Datum: 10. April 2016 um 20:49:25 MESZ
> An: mlippert@xxxxxxxxx
> 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=489467
> Product/Component: Community / Cross-Project
> 
> --- Comment #11 from David Williams <david_williams@xxxxxxxxxx> ---
> (In reply to Martin Lippert from comment #10)
>> Next iteration on this... :-)
>> 
>> My proposal for the category would be:
>> 
>> title:
>> "Cloud Tooling"
>> 
>> user facing description:
>> "Tools for developing apps for the cloud and in the cloud, including IDE
>> extensions, frameworks, container tools, and tools running the cloud
>> themselves."
>> 
>> internal criteria used projects that fit into this category:
>> 1. Cloud application and service management tool, including application
>> deployment.
>> 2. Frameworks for building, loading, managing, running, and executing
>> distributed tooling extensions with browser-client interfaces
>> 3. Extensions for programming languages, build systems, frameworks, ALM,
>> code assistant tools, and container tools that are running in the cloud or
>> are specifically build for working with the cloud.
>> 4. Tools and Cloud IDEs that orchestrate developer activity and development
>> workflow across distributed services.
> 
> This sounds ok to me, Martin. 
> Can you (or, CFT Team) create it, or need my help? 
> It must be created using the b3 aggregator, and when adding/removing features
> to any category, the b3 aggregator must be used since it modifies two files,
> you own and the main simrel.b3aggr file. (and both must be committed at same
> time to validate).
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.



Back to the top