Hi Benoît.
In general, code written by project committers does not require a
CQ. Figure 1 in the due diligence poster [1] tends to apply in this
case.
Written 100% by
Submitting Committer
or Committer on same
Project under the
supervision of the PMC
"supervision of the PMC" tends to mean that the contributions are
in-scope for the project and in-plan for the release. I believe that
this is the case here.
The IP team does not review the entire code base for a release.
The only time that you might consider creating a CQ for a
contribution made by an existing project committer is if they work
offline for an extended period (i.e. the contribution is developed
in private) or if you suspect that there might be some IP issues
with the contribution.
HTH,
Wayne
[1] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf
On 10/09/2013 04:18 AM, LANGLOIS Benoit
wrote:
Hello,
For your information about the release of PolarSys IDE 0.7 [1]:
- I've just submitted the source code of PolarSys IDE 0.7 for release review with IPZilla (IP bugzilla) [2].
- I've also generated the IP log for PolarSys IDE 0.7 which is also part of the process for a release review [3].
The objective is to release PolarSys IDE just before EclipseCon Europe.
I will keep you informed.
Benoît
[1] https://www.polarsys.org/projects/polarsys.3p/releases/polarsys-ide-0.7
[2] http://dev.eclipse.org/ipzilla/show_bug.cgi?id=7633 (restricted rights)
[3] https://www.eclipse.org/projects/ip_log.php?id=polarsys.polarsys.3p
_______________________________________________
polarsys-iwg mailing list
polarsys-iwg@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/polarsys-iwg
|