Greetings PMC.
The the EDP does not mandate that "1.0" means mature. That is, we
can turn this into a simple (first) release review if that makes
sense.
If there is concern about confusion in the community, the project
can opt to change the version name to "0.9" or something. But,
again, there is no requirement to do so.
Incubation branding rules would still be in effect.
Is this an option that you would consider, Etienne? Let us know if
you have questions.
Wayne
On 18/06/15 02:45 PM, David M Williams
wrote:
I hope other PMC
members take a look at
this request, and chime in, but I'll make some high level
comments.
I certainly have no objections to
the
project releasing, but given the version number of "1.0", I
assume
this review is not only for release, but also to graduate from
incubation.
Do you, (project lead and
mentors) really
think the project is ready to be a graduated, "stand alone"
project,
without continued mentorship?
I know I'm old-school, but would
list
the following references. I wonder if you've read them?
http://wiki.eclipse.org/Development_Resources/Process_Guidelines/What_is_Incubation
http://wiki.eclipse.org/Development_Resources/HOWTO/Incubation_Phase
http://wiki.eclipse.org/Development_Resources/HOWTO/Criteria_for_Graduating_from_Incubation_Phase_to_Mature_Phase
From what I can see in the
write-up,
I don't really see it.
I will admit I am biased, since
I'm
not sure how any project can prove "ready to graduate" after
only 2 months at Eclipse.
And, this project is obviously a
special
case, and perhaps does not fit into any Eclipse criteria
(reference points)
that I allows me to make a judgment?
Here's some things I found
anomalous:
- 69 bugs open and many of them
fixed
(that's good) but seemed that most were opened by 2 or 3 people
(not strong
evidence of "a community", in other words).
[I know in the past, you've
claimed
to have a community "outside of Eclipse" ... and if that's part
of the justification, then details should be given in the
documentation,
such as pointers to another bug
tracking
system? (Not sure that's good, to have another build tracking
system ...
just saying, if there's something "outside" of Eclipse that
demonstrates,
readiness to graduate, then I
think
should be included.]
- You had 4 "milestone builds"
but they were a week apart. That's not normally what we would
call a "milestone"
at Eclipse, so wonder what your definition is. Do you plan to
continue
to have weekly "milestones"?
If so, would be good to cover
that,
and define what that means, in your release/graduation review.
Given our history, about the
release
train, I was afraid to say anything, for fear of giving the
wrong impression
of being "not supportive" or "in the way".
But, I do really do mean these
remarks
as constructive.
And, I feel a responsibility to
"treat
all projects equally" and these are questions and things I would
look
at for any graduating project.
And, since no other PMC members
said
anything ... thought I should say something.
Hope you find my comments at
least a
little helpful, and again, would welcome comments from other PMC
members.
Thanks,
From:
Etienne Studer
<etienne@xxxxxxxxxx>
To:
Tools PMC mailing list
<tools-pmc@xxxxxxxxxxx>,
Date:
06/12/2015 06:39 PM
Subject:
[tools-pmc]
Request for approval of Buildship 1.0
Sent by:
tools-pmc-bounces@xxxxxxxxxxx
Hi
I would like to ask for review/approval of the release review
documentation
of Buildship 1.0:
https://projects.eclipse.org/projects/tools.buildship/reviews/1.0-release-review
Thanks and kind regards, Etienne_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/tools-pmc
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
|
