Re: [cross-project-issues-dev] Projects releasing other projects unrelea

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

I don't know if anyone from Sequoyah is
listening here, but this sounds like a fundamental problem with the Sequoyah
release. They are a mature project, containing bundles from an incubator.
As Wayne says below, this means Sequoyah downloads for Indigo must be indicated
as "Incubator" builds (egg logo, Incubator in feature names,
etc).

John

Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

06/09/2011 09:44 AM

Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	Re: [cross-project-issues-dev] Projects releasing other projects unreleased code .... ?

On Thu, Jun 9, 2011 at 9:25 AM, Wayne Beaton <wayne@xxxxxxxxxxx>
wrote:
If the project is copying the code from another project's
repository into their own repository, then a fork has occurred, and the
IP team needs to be informed (primarily for tracking purposes). In a general
sense, projects are permitted to take the output from other projects and
include it in their own distributions. If the project they are consuming
is in the incubation phase (does not apply here), then they are obligated
to include incubation branding in their own downloads.


Just an FYI, the xwt bundles *are* being consumed from an Incubation project,
the e4 Incubator, and have not graduated.

In the other mentioned case of org.eclipse.e4.core.di that bundle *did*
graduate to the Eclipse Project and is no longer in incubation.

Later,
PW

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev