A fellow Eclipse “technology” project does this:
Eclipse Nebula NatTable is a subproject of
Eclipse Nebula and does
Type A releases. But that would mean asking the technology PMC for setting up new Eclipse project(s) for Lyo.
–Andrew.
From: <lyo-dev-bounces@xxxxxxxxxxx> on behalf of Jad El-Khoury <jad@xxxxxx>
Reply-To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Date: Sunday, 17 September 2017 at 13:21
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Subject: Re: [lyo-dev] Type A diligence
Or a combination of both approaches.
There is no reason to move to Type A for Lyo/Core for example. It will only be a limited set of features (at the moment Lyo Validation only) that will be affected.
______________________________
Jad El-khoury, PhD
KTH Royal Institute of Technology
School of Industrial Engineering and Management, Mechatronics Division
Brinellvägen 83, SE-100 44 Stockholm, Sweden
Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45
jad@xxxxxx,
www.kth.se
From: lyo-dev-bounces@xxxxxxxxxxx [mailto:lyo-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jim Amsden
Sent: 14 September 2017 15:00
To: Lyo project developer discussions
Subject: Re: [lyo-dev] Type A diligence
Could we consider splitting the release into features: Lyo/Core, Lyo Generator, Lyo Validation, etc. with different IP diligence depending on the capability needs and usages?
This would allow API consumers to choose what features they need at what level of IP risk they can tolerate.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
From: Andrii Berezovskyi <andriib@xxxxxx>
To: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Date: 09/14/2017 06:40 AM
Subject: [lyo-dev] Type A diligence
Sent by: lyo-dev-bounces@xxxxxxxxxxx
Hello Lyo users & devs,
Right now, we are doing an IP review for the
Bug
519639 - Perform resource validation based on SHACL shapes. Eclipse IP team needs significant time to review all the Scala libraries that they have never seen before if we require them to
do a full Type B review.
IP team has suggested to me to do the review of the library using Type A diligence, which is somewhat less thorough.
If you are interested, please refer to
Wayne
Beaton’s blog post on due diligence. The gist of it is that diligence is selected on a release basis and if we decide to release 2.3.0 with Type A diligence, there is nothing preventing
us from releasing 2.4.0 later with the full Type B diligence.
I would like to hear from all of you if there are any major objections to doing a few releases with the lighter Type A diligence,
which will only check that all licenses are in order but will not do deep code scans for improperly copypasted code etc?
–Andrew.
(Lyo project lead)_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_lyo-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=xgy4nj5m_kJTOHN7s4QIytEQ1JlaarieVwljmSSD6d0&m=umQBS-MeFqeoF0JC74VToP1skP9SqsxZsi5--EVbeG8&s=nqlMuJZdUpGmjYooc4D6TD6R7-PszHOrBWAUHpVqqE8&e=