Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rt-pmc] CQ questions

1/ how is it possible to know the date of the last successful review date ?

Look at "Latest releases"; click the first "eye" in the review column and if the state is marked "approved", the date of that review is your last successful review date. 

2/ for Vert.x 4 that has API breakage, do we need a review or can we piggy back on 3.x release review done previously ?

Release type doesn't matter. After a successful release review, you can release for a year, outstanding intellectual property due diligence notwithstanding.
 

3/ if no release review is required by reusing a previous one : can we create a new release without a recent IP log submission if we are confident in the due current diligence ?

IP Log reviews are only required when you engage in a release review. You may request an IP Log review if you're not sure or want confirmation.

Theoretically, the project leadership chain (including the PMC) can compel you to engage in a release (or progress) review if they have concerns that they'd like reviewed.

HTH,

Wayne
 

On 5 Feb 2020, at 20:01, EMO EMO <emo@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Julien.

1/ "You may proceed to check the content into the Eclipse repository." is not clear enough, apparently. I'll work with the IP Team to improve this.

The short version is yes. When the IP Team says that you have "checkin" with this message, you can merge/push the content into a project repository and work with it. There are no restrictions with regard to branches.

The restriction is that a project must wait for project code content to be fully approved before it can be included in a release. You can do releases, they just can't include this content.

2/ IP log is scoped to the project, not any particular branch, release, component, ...  Think of the IP Log as an IP review checkpoint. When you submit that, we review it to make sure that the project team is properly tracking intellectual property and hasn't missed something important. FWIW, I run builds and match dependency lists from those builds against the IP Log.

It is completely valid for a project to have a CQ listed as "pending" on an IP Log when they do a release review. The content for pending (not yet approved) CQs must not, however, be included in the release.

Note that we changed the EDP in 2018 to permit a project to engage in as as many releases as necessary for an entire year following a successful release review. Every release, however, must conform to the IP Policy; specifically, the releases (whether or not we do a review specifically for that release) must only contain intellectual property that has been taken through the IP Due Diligence process (this means that any related CQs must be approved before you can release).

HTH,

Wayne

On Wed, Feb 5, 2020 at 11:04 AM Julien Viet <julien@xxxxxxxxxxxxxx> wrote:
Hi,

I do have a couple of questions related to the CQ for importing code.

1/ in the past some of our CQ got an initial approval for checkin:

"We have completed a high level triage of the attachment based on Parallel IP
[1].  You may proceed to check the content into the Eclipse repository.  We
will perform a comprehensive analysis at a later date based on IP work queue."

(source https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21001)

Do we need to wait for this comment to check in the submitted code in the master branch of the repository (given we don't want to do a release of master) ?

2/ submitting an IP log requires is scoped to a project and not to a branch of the project.

We are in the case where we are aiming doing a 3.9 release and thus we will submit an IP log review + a release review. If we have unresolved CQ targeting the master branch (e.g the DB2 contribution CQ) would those conflict a conflict for a 3.9 release or not ?

thanks for clarifying

Julien
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rt-pmc


--
The Eclipse Management Organization
Eclipse Foundation
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rt-pmc

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/rt-pmc


--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Back to the top