| [lyo-dev] Type A diligence |
|
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) |