[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-pmc] Checklist for release reviews
|
Also, I don't think we all have
to perform every review that comes through the PMC... Maybe we want
to for these first ones just to get familiar with the overall effort. But,
my experience with MicroProfile is that we just need one +1 from a PMC
member. Once we get the one positive vote, then we're feeling pretty
good from a PMC viewpoint. I suppose someone could come along and
do a -1 before the actual Review, but I wonder how common that is once
someone has given a +1?
---------------------------------------------------
Kevin Sutter
STSM, MicroProfile and Java EE architect
e-mail: sutter@xxxxxxxxxx Twitter: @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)
LinkedIn: https://www.linkedin.com/in/kevinwsutterFrom:
Wayne Beaton <wayne.beaton@xxxxxxxxxxxxxxxxxxxxxx>To:
EE4J PMC Discussions
<ee4j-pmc@xxxxxxxxxxx>Date:
11/08/2018 09:40 AMSubject:
Re: [ee4j-pmc]
Checklist for release reviewsSent by:
ee4j-pmc-bounces@xxxxxxxxxxx
We have a checklist in the handbook.
You'll note that this checklist is pretty generic. The EMO uses this (roughly)
as part of our review. It would be helpful if the PMC could alert the EMO
if they know that the project is falling short on any particular item,
but we don't certainly expect the PMC to go through every line of this
checklist.
Where we need the PMC's help is in confirming that project- and TLP-specific
things are being observed, e.g., validation that the project is operating
within the charter of the Top Level Project, and within the bounds of its
own scope. In most cases, you should be able to determine whether or not
this is true by just reading the description of the release. i.e. it shouldn't
take more than a couple of minutes.I do need a little extra help from the PMC to ensure that
project releases do not violate the current and any future trademark agreement
that we have with Oracle. Note that it is generally the case that Eclipse
projects cannot violate trademarks owned by other organizations; getting
some help from the PMC to do this would be great, but I understand that
it can be time consuming (I don't expect the PMC to go line-by-line through
code). I'm thinking that we'll make this a required checkbox in the release
record and require that the Project Lead attest that the project code and
documentation does not violate trademarks owned by others (or something
like that). In the meantime, maybe it's enough to let this paragraph serve
as a reminder for project leads that this is an issue.The request for approval is also a good opportunity for
the PMC to make comments and recommendations regarding growing the diversity
of project committers or other health metrics, conformance to best practices,
technical direction, etc.WayneOn Thu, Nov 8, 2018 at 5:34 AM Steve Millidge (Payara)
<steve.millidge@xxxxxxxxxxx> wrote:Now all the release reviews are coming. Do we have a simple
checklist for what we need to check before voting?
I know it was discussed just checking whether we have something
before I review the EDP.
Thanks
Steve Millidge
Founder
Payara Services Limited
Payara Micro – Small, Simple, Serious
W: www.payara.fish| T: +44
207 754 0481 ; +1 415 523 0175 | M: +44 7920 100 626 | Twitter: @Payara_Fish
Registered in England and Wales: 09998946,
Registered Office: Malvern Hills Science
Park, Geraldine Road, Malvern, Worcestershire, WR14 3SZ
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
--
Wayne Beaton
Director of Open Source Projects
| Eclipse Foundation, Inc.
Meet us at EclipseCon
Europe 2018:
LUDWIGSBURG, OCTOBER 23 - 25_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc