Community
Participate
Working Groups
We'll use this bug to track the release We require IP Team approval of the IP Log. We require PMC approval of the release and review materials. There's help regarding releases in the handbook. https://www.eclipse.org/projects/handbook/#release
We changed the way reviews work in the Eclipse Foundation Development Process in December 2018 [1]. Following a successful release review (e.g., the October 2019 0.17 release) an Eclipse project may release as many times as they need to for a period of one year. So this review isn't actually required. If the project team feels that a review is desired, we can continue. That's entirely left to your discretion. Note that, whether or not you engage in a release review, the intellectual property must be fully vetted (e.g., CQs must be approved) before the content may be included in a release. Following the Eclipse Foundation's Board of Directors approval of the IP Policy in October 2019, we no longer distinguish between "Type A" and "Type B" IP due diligence for third party content. I have therefore changed the release and project due diligence type to "Type A". [1] https://www.eclipse.org/projects/dev_process/#6_4_Releases
There is a new CQ for this release so I created a IP Log for review. https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21338
(In reply to Peter Shipton from comment #2) > There is a new CQ for this release so I created a IP Log for review. > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21338 The IP Log is not required. We only require that the project lead(s) ensure that the content contained in the release has been vetted (e.g., the CQ has been approved) before you push out the release. An IP Log review is only required when you engage in a release or progress review, or if you are otherwise concerned that the intellectual property state of the project should be validated. I appreciate your patience as we work out the change in process (and corresponding documentation updates) to accommodate to the policy changes.
