I've already updated twice. I will do one last update at RC2.
On 21/04/2010 16:22, Kenn Hussey wrote:
Project leads, please take the necessary action for your
projects based on David's email below. Note that this involves updating
all of your feature.properties, license.html, and notice.html files. As
far as I understand it, the contents of your license.html and
notice.html files should be identical (based on the new one attached to
the bug referenced below).
Sorry for the churn. The new SUA is
not radically different, but has some
important clarifications about
of Eclipse's provisioning system.
Well, you know ... important for
reasons, hence required for us.
And, in case you are wondering, yes
it was considered to "push back" on
this request, but I think there is
enough time to accommodate it, without
endangering our Simultaneous Release
so best to take advantage of
the timing to get current and
----- Forwarded by
M Williams/Raleigh/IBM on 04/21/2010 10:16 AM -----
Of course, this applies to those features that use the Eclipse SUA and
if someone was shipping a feature in Helios that didn't use that, then
you wouldn't want to change yours .... but, then I'd wonder why it was
For reference, see http://eclipse.org/legal/guidetolegaldoc.php
for details on the legally required documents ... but, this Helios
goes beyond the minimum requirement and gets us all to use the exact
text, so the software can tell when its really the same license.
If you try to get the "standard text" from the website, you need
to be careful to get the plain HTML and ASCII versions, make sure
no web encoding conversion errors, etc., so probably easiest to get
the bugzilla entry.
One disturbing angle that's come up, while some checked if we all use
same text, is that some of you are not using ANY (yet). That is really
a big "no no" and would be a "stop ship" issue, if
found "at the last minute" (as far as I know,
it should be a stop ship issue even for milestones, etc ... but, I'm
here to judge ... yet).
So, let's try to get this all corrected for M7, so we don't have to
around with this routine level of detail for release candidates. Plus,
if you fix yours for M7, that'll make all the slackers really standout
in M7 and we can more easily see who they are :)