[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-dev] Converting the platform to the EPL license
|
Kevin,
can you clarify the following sentence:
>Once this CPL-only code is removed, each component can update their CPL
copyright statements to reflect the EPL license.
Does it mean as soon as a/my component is free of CPL-only code it can be
migrated or does it mean it has to wait until the code is gone from all
components?
Thanks,
Dani
Kevin Haaland
<Kevin_Haaland@ca
.ibm.com> To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin cc
@eclipse.org
Subject
[eclipse-dev] Converting the
21.02.2005 19:38 platform to the EPL license
Please respond to
eclipse-dev@eclip
se.org
The Eclipse Foundation has given the Eclipse Platform approval to proceed
on converting to the EPL license. We will do this work in the 3.1 HEAD
stream. Here are the two steps we will perform:
First, we need to ensure that any contributions that were not made
available under the EPL are removed. There are 4 contributions that have
this characteristic:
bug 12745 - CVS/Entries file timestamp day field not space padded
bug 14735 - recursive folder resource creation
bug 22122 - [resources] IResourceChangeDelta does not handle replaces/move
correctly
bug 68737 - Double clicking stack frame in JUnit failure trace should
display source [JUnit]
We will independently implement new fixes to these defects as soon as
possible.
Once this CPL-only code is removed, each component can update their CPL
copyright statements to reflect the EPL license.
Sonia has updated the release engineering tools to automate the updating of
the copyright statements. You can get the latest version here:
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/platform-releng-home/org.eclipse.releng.tools_3.1.0.zip?rev=1.1
