You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Markus Weimer <ma...@weimo.de> on 2015/08/29 01:13:20 UTC
Breaking changes by removing APIs that can't possibly work right now?
Hi,
we have many APIs in REEF.NET that can't possibly work right now, mostly
involving properties which have a setter that we can't support. I filled
and collected many of them under REEF-686.
Going through the whole deprecation cycle for this seems like a fool's
errand, as those APIs don't work right now. Hence, I propose to remove
them directly, without waiting for a release.
Thoughts?
Markus
Re: Breaking changes by removing APIs that can't possibly work right
now?
Posted by Markus Weimer <ma...@weimo.de>.
Hi,
this has been standing on the list for a while. I assume we can hence go
ahead and act on REEF-686 with extreme prejudice :-)
Markus
On 2015-08-28 20:04, Brian Cho wrote:
> I like this idea. +1
>
> -Brian
>
> On Sat, Aug 29, 2015 at 8:47 AM, Byung-Gon Chun <bg...@gmail.com> wrote:
>
>> That sounds good to me.
>>
>> Sent from my iPhone
>>
>> 2015. 8. 29. 오전 8:13 Markus Weimer <ma...@weimo.de> 작성:
>>
>>> Hi,
>>>
>>> we have many APIs in REEF.NET that can't possibly work right now, mostly
>>> involving properties which have a setter that we can't support. I filled
>>> and collected many of them under REEF-686.
>>>
>>> Going through the whole deprecation cycle for this seems like a fool's
>>> errand, as those APIs don't work right now. Hence, I propose to remove
>>> them directly, without waiting for a release.
>>>
>>> Thoughts?
>>>
>>> Markus
>>
>
Re: Breaking changes by removing APIs that can't possibly work right now?
Posted by Brian Cho <ch...@gmail.com>.
I like this idea. +1
-Brian
On Sat, Aug 29, 2015 at 8:47 AM, Byung-Gon Chun <bg...@gmail.com> wrote:
> That sounds good to me.
>
> Sent from my iPhone
>
> 2015. 8. 29. 오전 8:13 Markus Weimer <ma...@weimo.de> 작성:
>
> > Hi,
> >
> > we have many APIs in REEF.NET that can't possibly work right now, mostly
> > involving properties which have a setter that we can't support. I filled
> > and collected many of them under REEF-686.
> >
> > Going through the whole deprecation cycle for this seems like a fool's
> > errand, as those APIs don't work right now. Hence, I propose to remove
> > them directly, without waiting for a release.
> >
> > Thoughts?
> >
> > Markus
>
Re: Breaking changes by removing APIs that can't possibly work right now?
Posted by Byung-Gon Chun <bg...@gmail.com>.
That sounds good to me.
Sent from my iPhone
2015. 8. 29. 오전 8:13 Markus Weimer <ma...@weimo.de> 작성:
> Hi,
>
> we have many APIs in REEF.NET that can't possibly work right now, mostly
> involving properties which have a setter that we can't support. I filled
> and collected many of them under REEF-686.
>
> Going through the whole deprecation cycle for this seems like a fool's
> errand, as those APIs don't work right now. Hence, I propose to remove
> them directly, without waiting for a release.
>
> Thoughts?
>
> Markus