[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ecf-dev] ECF API and feature freeze
|
Hi Markus,
Markus Alexander Kuppe wrote:
<stuff deleted>
In the meantime, I talked to the RT PMC and the bottom line is, that the
decision is up to the individual projects and their respective ramp down
policies [0]. However they ask us to consider the effects a late
addition has on the overall quality of the Helios simultaneous release.
Based on the current shape of the ZooDiscovery in terms of tests
("compliance" with ECF discovery test suite), code coverage [1] and the
early adoption is has seen while hosted at OSU, as well as the fact that
it does not constitutes an API or feature change, I'm +1 for making it
part of Helios.
I'm +1 for making the ZooDiscovery provider part of Helios as well.
PLEASE NOTE: All other ECF committers...please vote on this also. If
you want/need explanation of what this is for please see below.
Scott
Explanation
As part of the ECF ramp-down policy [0], at this stage of the Helios
Simultaneous Release (M7 has occurred), changes/additions to ECF's
contribution to the simultaneous release need to be approved by a vote
of the committers. What's under consideration here is the addition of
the Apache Zookeeper-based ECF discovery provider. This includes *no*
changes/additions to the discovery API itself, but rather a new
implementation/provider for the Discovery API based upon the Apache
Zookeeper protocol).
Markus
[0] http://wiki.eclipse.org/ECF_3.0.0/Galileo_Ramp-Down_Policy
[1] https://ecf2.osuosl.org/hudson/job/C-HEAD-discovery.zookeeper.feature
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
