[cft-dev] Breakdown of CFT third-party dependencies

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cft-dev] Breakdown of CFT third-party dependencies - Planning Council

From: Nieraj Singh <nsingh@xxxxxxxxxx>
Date: Wed, 24 Feb 2016 18:16:41 -0800
Delivered-to: cft-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cft-dev>
List-help: <mailto:cft-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cft-dev>, <mailto:cft-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cft-dev>, <mailto:cft-dev-request@eclipse.org?subject=unsubscribe>

I've updated the bugzilla entry that lists all the third-party
dependencies currently used by CFT, and which can be consumed from
Orbit, which may be updated to be used from Orbit, and those that have
no entries in Orbit. This information is for the Planning Council for
getting an exception for inclusion into Neon Simultaneous Release.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=488054

Follow-Ups:
- Re: [cft-dev] Breakdown of CFT third-party dependencies - Planning Council
  - From: Nieraj Singh

Prev by Date: [cft-dev] March 16 - CFT deadline for Neon M6 aggregate build
Next by Date: [cft-dev] Minimum Eclipse target for building CFT
Previous by thread: [cft-dev] March 16 - CFT deadline for Neon M6 aggregate build
Next by thread: Re: [cft-dev] Breakdown of CFT third-party dependencies - Planning Council
Index(es):
- Date
- Thread

Breadcrumbs