| Re: [eclipse.org-architecture-council] How to trigger a progress review? |
We added progress reviews primarily to satisfy requirements of the specification process but, frankly, haven't actually needed them before now.I've opened an issue against the PMI to support them in a first-class manner. In the meantime, you can either email EMO or indicate in your IP Log review submission that you'd like to initiate a progress review, and I'll create the record for you.FWIW, progress reviews are the same as release reviews in all respects but alignment with a release. That is, following a successful review, the project can create as many releases as necessary.Note that, even though a review is not required for every release and--by extension--an IP Log review is not required, the project team must ensure that the intellectual property contained in and referenced by the release content has all been fully vetted by the IP Due Diligence process. The Eclipse Dash License Tool can help with this; Alexander recently contributed some content to the README that describes how to incorporate the tool in your Maven builds (there's help to support other types of technology as well). Bear in mind that the tool has limitations and is intended to assist with the process of validating the licenses of third-party content; we ultimately depend on committers to know what content they're leveraging.While I have your attention, I've added some functionality to the license tool that automatically generates IP vetting requests and sends them to the "IPLab" repository on GitLab. I haven't added this to the documentation yet as we're not ready to handle a deluge of requests (as it is, the feature throttles the number of requests that it will send). As part of this experiment, we're removing the PMC approval requirement. At this point, the actual vetting process is entirely manual, so the overall speed at which requests are processed may not be faster, but that's the direction that we're heading in. I'll ask you to please not leverage this feature in CI, at least not for now. For one, you need to use a GitLab token that you need to be careful not to share.HTH,
WayneOn Thu, Feb 25, 2021 at 11:32 AM Mickael Istria <mistria@xxxxxxxxxx> wrote:_______________________________________________Hi all,I'd like to progressively move some projects I'm working on away from Release Reviews, which -although they happen once a year- are delaying releases and cascading to a whole chain of delays that's not comfortable when approaching a deadline.Instead, I'd like to move as much as possible to Progress Reviews ( https://www.eclipse.org/projects/dev_process/#6_3_5_Progress_Review ) that I can trigger every year without messing up with the release schedule, delays, deadline... Basically uncoupling as much as possible releases and necessary yearly reviews. Progress Reviews seem perfect for that.My concern is that although it's documented in the EDP, I see no practical way of triggering, scheduling, announcing... a Progress Review in the PMI. Basically, how does it work in practice?Thanks in advance
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
--_______________________________________________Wayne Beaton
Director of Open Source Projects | Eclipse Foundation
eclipse.org-architecture-council mailing list
eclipse.org-architecture-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-architecture-council