Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Documentation and signing requirements for Mars

BTW, the new launch bar feature isn’t signed yet. I’ll work on that today.

Doug.

From: Wayne Beaton <wayne@xxxxxxxxxxx>
Organization: The Eclipse Foundation
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Tuesday, May 5, 2015 at 11:44 AM
To: "cross-project-issues-dev@xxxxxxxxxxx" <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] Documentation and signing requirements for Mars

Many of the entries on the "unsigned" report [1] are features.

Features must also be signed.

Please check if your features are on the list. Note that the report doesn't include a path or make any particular distinction for features. I chased a plug-in for a solid hour yesterday before I noticed that there was a feature with exactly the same id (but with a different version number).

David, perhaps some future version of the tool can include more of the file path or some indication of feature vs. plug-in.

Wayne

[1] https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/lastSuccessfulBuild/artifact/aggregation/final/buildInfo/reporeports/reports/verifydiroutput/unsigned8.txt

On 29/04/15 04:40 PM, Wayne Beaton wrote:
READ THIS AND TAKE ACTION IF YOU ARE PARTICIPATING IN THE MARS SIMULTANEOUS RELEASE.

It looks like a few features aren't implementing the rules of participation [1]. If your project does not conform to the rules, it will fail the release review. If it does not make sense for your project to conform to the documentation and signing requirements, I will expect this to be documented in the release review materials and explicitly approved by your PMC.

Frankly, I'm primarily concerned with making sure that the legal documentation requirements are met and that the user experience has the fewest number of surprises.

To that end, please look at these reports. Focus on the "Bundles missing required files", "Unsigned JARs", "Feature Copyrights", and "Consistent, current licenses (SUA) in features" links. Resolve these first and then look at the rest of entries to make sure that you're getting them right as well.

I feel very strongly that every feature should have a description that's better than "My feature". Describe the feature with one or two sentences.

David, feel free to add your concerns to this list.

I've got some bugs open on some SUA problems. If I've opened a bug against your project, please deal with it ASAP.

Upcoming dates reminder:

May 22/2015 - IP Log submission deadline
May 29/2015 - Review materials due
June 12/2015 - Release Review

Thanks,

Wayne

[1] https://hudson.eclipse.org/simrel/job/simrel.mars.runaggregator.CLEAN_BUILD/60/artifact/aggregation/final/buildInfo/reporeports/index.html
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon France 2015


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon
          France 2015
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Back to the top