Re: [cross-project-issues-dev] Remember to update your feature.propertie

[Brian Payton <bpayton@xxxxxxxxxx>]

Hello David,

Regarding the "fix-up licenses"
tool, org.eclipse.wtp.releng.fixups:  it works great, but please change
the bundle-version entry in the MANIFEST.MF for org.eclipse.ui.console
to something like "[3.0.0,4.0.0)".  As it is, with the required
bundle version of exactly 3.5.0, it will only deploy to Eclipse 3.6.  (I'm
probably not the only person who is using Eclipse 3.5.2 as my primary IDE
until 3.6 is GA.)

Regards,
Brian

Brian Payton
Data Tools Development
IBM Silicon Valley Laboratory





From:      
 David M Williams/Raleigh/IBM@IBMUS
To:      
 Cross project issues
<cross-project-issues-dev@xxxxxxxxxxx>
Date:      
 04/24/2010 03:40 PM
Subject:    
   Re: [cross-project-issues-dev]
Remember to        update      
 your        feature.properties
file, to use consistent licensing text
Sent by:    
   cross-project-issues-dev-bounces@xxxxxxxxxxx

---

I left out one link ... depending on what you meant by "specific,
detailed, clear explanation"
... you can just use 
the ones at the normal Eclispe "legal documents" web site ...
the plain HTML and feature.properties files linked from right hand 
side of 

http://eclipse.org/legal/epl/notice.php

They have been updated now. 

Thanks,

From:	David M Williams/Raleigh/IBM@IBMUS
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	04/24/2010 05:39 PM
Subject:	Re: [cross-project-issues-dev] Remember to update        your        feature.properties file, to use consistent licensing text
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Yes, this has been clarified or specified via bug 306627
https://bugs.eclipse.org/bugs/show_bug.cgi?id=306627

and there is a small tool to help, as described at 
http://wiki.eclipse.org/WTP/Releng/Tools#Check_and_fix-up_licenses_tool

In general, what is required for release is defined in 
http://eclipse.org/legal/guidetolegaldoc.php

The Simultaneous Release requirement was just one small addition to what
is normally required for "legal documents". 
It basically said everyone must use the same SUA text. Historically, we
all sort of drifted to using "different" ones, that 
only differed in capitalization used, perhaps some date, and special characters
like bullets or "trademark". 
And this made things hard for end-users who might be looking to read each
distinct license ... as they are supposed to do :). 

>From what I've seen, this "consistent license" requirement
has brought to light many issues or projects that are not 
compliant in general about having the right license files or about files
.... so I hope no one falls into a trap of 
thinking "oh, we have consistent SUA license now, so we are done".
You do still need to meet _all_ 
the normal requirements as detailed in 
http://eclipse.org/legal/guidetolegaldoc.php
The consistent license requirement was just one small addition. 

Thanks,

From:	Scott Lewis <slewis@xxxxxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	04/22/2010 12:52 PM
Subject:	Re: [cross-project-issues-dev] Remember to update your        feature.properties file, to use consistent licensing text
Sent by:	cross-project-issues-dev-bounces@xxxxxxxxxxx

---

Hey all,

Is there a specific, detailed, clear explanation of what has to be done
by simultaneous release projects to meet this requirement...and pointers
to any available tools to support the required changes?  e.g. changes
to 
features (all/subset...which?), plugins (all/subset...which?)

Sorry if this information appears earlier in the mailing list (if so, 
please just link to it) but I haven't been able to read all traffic.

Thanks,

Scott


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev