Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ecf-dev] Rest API additions - COMMITTERS PLEASE VOTE ASAP

Hi Folks,

There is a consumer of the REST API that would like to add a small 
amount of API in order to introduce flexibility into the handling of 
default parameters [1].  It would be convenient for them for this 
addition to be in Helios release (ECF 3.3) and so I propose that we add 
this API to our Helios release stream.  There's a brief explanation of 
changes and risks below, and see the bug [1] for details.

Since we are after M7, however, and our ramp-down policy [2] states that 
any API changes have to be approved by vote of committers, I'm hereby 
requesting such a vote.  *If you are a committer*, please vote (+1, 0, 
-1) in response to this email as soon as possible.

My (Scott) vote:  +1

Thanks,

Scott

Explanation of Changes and Risks

The changes are *additions* to the API (protected methods added to 
abstract superclass).  Existing client will not be affected.  I consider 
the risks low...and it seems likely that this API will be used by other 
consumers of the ECF REST API.


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=312482
[2] http://wiki.eclipse.org/ECF_3.0.0/Galileo_Ramp-Down_Policy 


Back to the top