So, you want to replace the PMC with a bot? :-)
I expect different PMC members to have different things that are
important to them, and thus make their own independent judgments as
to whether a release should be approved.
But yes, it would still be good to publish some guidelines for what
the PMC expects out of a project. It won't be complete or
algorithmic or definitive, but it will provide the projects some
guidance.
Markus KARG wrote on 09/12/18 10:36 AM:
Thanks
Wanye for this kind explanation! :-)
But
I literally meant what I wrote: Does the EE4J PMC have a
checklist to follow in the release review?
If
yes, I would like to see it published. If no, I wonder how
the EE4J PMC guarantees that the job you describe is
performend by all PMC members in the same way. The risk I
see is that some PMC members could do more different checks
than other PMC members, but we should guarantee that all
EE4J subprojects go through the exact same PMC review steps
always, independent of the actual PMC member performing the
checks.
Thanks
-Markus
Every PMC determines their own process
and checklist for reviews.
I suspect though, that you're more
interested in understanding what we expect projects to do
to prepare for a release review. We do have a checklist, but it's heavily
rooted in our history of most of our projects building Eclipse
Platform Plug-ins. If you ignore the bits about
bundles and plug-ins, though, it's a pretty good start
(further generalizing this checklist is on my to do
list).
The EMO does a lot of the actual
checking, but we lean on the PMC to assess that the
project is working within their scope, is following the
rules of the EDP (the open source rules of engagement in
particular), and is just generally doing the right sorts
of things to develop community. Again, it's up to the PMC
to determine how to assess this.
We purposely keep the formality to a
minimum. A project team representative asks the PMC for
approval of their release and corresponding Release Review
materials on the PMC mailing list. The EMO waits for any
related discussion to settle; once it's clear that the PMC
has given their approval, we move forward with the
review.
Once we have the approvals that we
require (PMC approval of the release and IP Team approval
of the IP Log), we schedule the review. Reviews conclude
after one week of being open for community feedback. The
date that we assign to a review is the end date of the
community feedback period. We schedule those dates on the
first and third Wednesdays of every month.
On Tue, Sep 11, 2018 at 5:20 PM, Markus
KARG <markus@xxxxxxxxxxxxxxx>
wrote:
Is
there a documented process or check list regarding
what stuff actually the PMC member must check in a
release review?
-Markus
--
Java Champion, JCP EC/EG Member, EE4J PMC,
JUG Leader
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
--
Wayne Beaton
Director of Open Source Projects
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-pmc
|
