Re: Freezing platform API changes until second donation is complete?

[Antonio]

Exactly. I think we all want those plugins to work on Apache NetBeans.

I propose marking PRs that require API changes as such from now on 
(there's a Github label for that), so we can perform a review to see if 
those changes are indeed incompatible.


Cheers,
Antonio

On 16/03/18 09:14, Jaroslav Tulach wrote:

Hello Antonio.
Preventing any API changes would de-facto stop most of the development for
an unknown period (who knows how long the 2nd donation will take, I don't
dare to estimate). However I understand your concern I also use many
modules from 8.2 (JavaScript, Python, Eclipse formatter, etc.) in the
latest development build and I want them to work.

Luckily we don't have to freeze the API. We just need it to be compatible.
Thus I suggest to ban any _incompatible changes_ (especially to publicly
available signature).

We do that most of the time, but these days it is more important. We really
have a "business reason" to keep compatibility. There are tons of plugins
written against 8.2 and nobody is going to rewrite them to new NetBeans
version anytime soon (never in some cases).

If we keep binary backward compatibility, we will be sure that old plugins
(at least) link with new NetBeans.
-jt


2018-03-16 8:52 GMT+01:00 Antonio :


Hi all,

I was wondering if we should freeze PRs that change the platform API until
the second code donation is complete: many users still use plugins from
NetBeans 8.2 on top of the Apache NetBeans 9.0 Beta Platform (through the
update center).

Thanks,
Antonio

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists








-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Freezing platform API changes until second donation is complete?

[Jaroslav Tulach]

Hello Antonio.
Preventing any API changes would de-facto stop most of the development for
an unknown period (who knows how long the 2nd donation will take, I don't
dare to estimate). However I understand your concern I also use many
modules from 8.2 (JavaScript, Python, Eclipse formatter, etc.) in the
latest development build and I want them to work.

Luckily we don't have to freeze the API. We just need it to be compatible.
Thus I suggest to ban any _incompatible changes_ (especially to publicly
available signature).

We do that most of the time, but these days it is more important. We really
have a "business reason" to keep compatibility. There are tons of plugins
written against 8.2 and nobody is going to rewrite them to new NetBeans
version anytime soon (never in some cases).

If we keep binary backward compatibility, we will be sure that old plugins
(at least) link with new NetBeans.
-jt


2018-03-16 8:52 GMT+01:00 Antonio :

> Hi all,
>
> I was wondering if we should freeze PRs that change the platform API until
> the second code donation is complete: many users still use plugins from
> NetBeans 8.2 on top of the Apache NetBeans 9.0 Beta Platform (through the
> update center).
>
> Thanks,
> Antonio
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>