I can't say I'm keen to give this a +1.
Is there some user facing documentation that highlights the breaking change and the action the user needs to take? Or is that something that will just be mentioned in the release notes?
I didn't see a post about this in the ECF community forum ([1]). Or do you think the majority of ECF users hang out on ecf-dev?
Why not simply bump your version to acknowledge the breaking change? (I did that for Gemini Blueprint 2.0 because a bug fix was mildly incompatible, so you can see where I'm coming from!)
Regards,
Glyn
Hi,
ECF is going to have its service release 3.6.1 end of month.
After a discussion during one of our regular conf calls [1] and a
notification on the ecf-dev mailing list last week [2] in which the
community hasn't vetoed this API change, we decided to include a
(breaking) change in our REST based remote service API in 3.6.1.
The bug [3] itself has a simple and straight forward migration path and
thus is low risk, while simultaneously allowing users to address more
sophisticated usecases.
All in all, we would like to get consent for this change from the RT
pmc. Please +1.
Thanks
Markus
[1] http://dev.eclipse.org/mhonarc/lists/ecf-dev/msg06298.html
[2] http://wiki.eclipse.org/ECF_Conference_Call_5.14.2013
[3] https://bugs.eclipse.org/408034
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|
