CDT 10.0 and API breaking changes (Coming soon?)

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

CDT 10.0 and API breaking changes (Coming soon?)

Jonah Graham
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Jonah Graham
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Mark B
it seems a good idea, we could do a grep in the code to detect the deprecated methods and remove them. Have we got a list of things "change at next major version" anywhere? We could change and clean up some parts.

Il mer 22 gen 2020, 16:35 Jonah Graham <[hidden email]> ha scritto:
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Jonah Graham
The process needs to be some way of recording what we plan to delete. We can do it on a wiki page, or in bugzilla with a keyword/milestone. In the end we need to publish API changes as part of the N&N at a minimum. 

The Eclipse Platform team have an ongoing process where API is deprecated and removed over a multi-year process. This allows them to remove API in any release without even having to have a major release. 

Therefore we have some process decisions to make:

- Adopt Platform policy for API Deprecate and Deletion (see https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy)
- Aim to do everything for Major version release (as done before in CDT)
- Do both (e.g. have major release and then continuously follow platform policy)

The other question is when?

I am very interested in what people's opinions are now - then we can formalize the process.

Thanks,
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 13:23, Mark B <[hidden email]> wrote:
it seems a good idea, we could do a grep in the code to detect the deprecated methods and remove them. Have we got a list of things "change at next major version" anywhere? We could change and clean up some parts.

Il mer 22 gen 2020, 16:35 Jonah Graham <[hidden email]> ha scritto:
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Aleksandar Kurtakov


On Thu, Jan 23, 2020 at 9:29 PM Jonah Graham <[hidden email]> wrote:
The process needs to be some way of recording what we plan to delete. We can do it on a wiki page, or in bugzilla with a keyword/milestone. In the end we need to publish API changes as part of the N&N at a minimum. 

The Eclipse Platform team have an ongoing process where API is deprecated and removed over a multi-year process. This allows them to remove API in any release without even having to have a major release. 

Therefore we have some process decisions to make:

- Adopt Platform policy for API Deprecate and Deletion (see https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy)
- Aim to do everything for Major version release (as done before in CDT)
- Do both (e.g. have major release and then continuously follow platform policy)
As CDT hasn't done that for years "Do both" is best as it will give some head start and major release to indicate the change of policy too.
 

The other question is when?

I am very interested in what people's opinions are now - then we can formalize the process.

Thanks,
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 13:23, Mark B <[hidden email]> wrote:
it seems a good idea, we could do a grep in the code to detect the deprecated methods and remove them. Have we got a list of things "change at next major version" anywhere? We could change and clean up some parts.

Il mer 22 gen 2020, 16:35 Jonah Graham <[hidden email]> ha scritto:
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev


--
Alexander Kurtakov
Red Hat Eclipse Team

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Alexander Fedorov
+1 for "Do both" and the major switch should be well prepared.

Currently we are still inside the "made an inventory" activity, you can see a number of email regarding status for particular component. This is a kind of "top-to-bottom" process for the moving target that may require a lot of time to converge.
I suggest to start also the "bottom-to-top" activities to mark API types for deletion with clear annotation/comment which version is planned to apply the actual deletion. This will allow us to see the difference between "deprecated" and "to be deleted" types. I do recommend to not consider particular field or method for deletion - only the whole type, this way we will have theoretical ability to have "compat" fragments to give a longer time for migration.

Regards,
AF

23.01.2020 22:45, Aleksandar Kurtakov пишет:


On Thu, Jan 23, 2020 at 9:29 PM Jonah Graham <[hidden email]> wrote:
The process needs to be some way of recording what we plan to delete. We can do it on a wiki page, or in bugzilla with a keyword/milestone. In the end we need to publish API changes as part of the N&N at a minimum. 

The Eclipse Platform team have an ongoing process where API is deprecated and removed over a multi-year process. This allows them to remove API in any release without even having to have a major release. 

Therefore we have some process decisions to make:

- Adopt Platform policy for API Deprecate and Deletion (see https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy)
- Aim to do everything for Major version release (as done before in CDT)
- Do both (e.g. have major release and then continuously follow platform policy)
As CDT hasn't done that for years "Do both" is best as it will give some head start and major release to indicate the change of policy too.
 

The other question is when?

I am very interested in what people's opinions are now - then we can formalize the process.

Thanks,
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 13:23, Mark B <[hidden email]> wrote:
it seems a good idea, we could do a grep in the code to detect the deprecated methods and remove them. Have we got a list of things "change at next major version" anywhere? We could change and clean up some parts.

Il mer 22 gen 2020, 16:35 Jonah Graham <[hidden email]> ha scritto:
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev


--
Alexander Kurtakov
Red Hat Eclipse Team

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
Reply | Threaded
Open this post in threaded view
|

Re: CDT 10.0 and API breaking changes (Coming soon?)

Jonah Graham
Hello folks,

As we decide process and timelines over the coming weeks I don't want to lose some of the information that has already been collected. 

Therefore, if you have a bug report on removing some code in CDT 10.0, can you add it to Bug 559549.

(BTW I am sort of in the Do Both camp too)

Thank you,
Jonah
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Fri, 24 Jan 2020 at 04:58, Alexander Fedorov <[hidden email]> wrote:
+1 for "Do both" and the major switch should be well prepared.

Currently we are still inside the "made an inventory" activity, you can see a number of email regarding status for particular component. This is a kind of "top-to-bottom" process for the moving target that may require a lot of time to converge.
I suggest to start also the "bottom-to-top" activities to mark API types for deletion with clear annotation/comment which version is planned to apply the actual deletion. This will allow us to see the difference between "deprecated" and "to be deleted" types. I do recommend to not consider particular field or method for deletion - only the whole type, this way we will have theoretical ability to have "compat" fragments to give a longer time for migration.

Regards,
AF

23.01.2020 22:45, Aleksandar Kurtakov пишет:


On Thu, Jan 23, 2020 at 9:29 PM Jonah Graham <[hidden email]> wrote:
The process needs to be some way of recording what we plan to delete. We can do it on a wiki page, or in bugzilla with a keyword/milestone. In the end we need to publish API changes as part of the N&N at a minimum. 

The Eclipse Platform team have an ongoing process where API is deprecated and removed over a multi-year process. This allows them to remove API in any release without even having to have a major release. 

Therefore we have some process decisions to make:

- Adopt Platform policy for API Deprecate and Deletion (see https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy)
- Aim to do everything for Major version release (as done before in CDT)
- Do both (e.g. have major release and then continuously follow platform policy)
As CDT hasn't done that for years "Do both" is best as it will give some head start and major release to indicate the change of policy too.
 

The other question is when?

I am very interested in what people's opinions are now - then we can formalize the process.

Thanks,
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 13:23, Mark B <[hidden email]> wrote:
it seems a good idea, we could do a grep in the code to detect the deprecated methods and remove them. Have we got a list of things "change at next major version" anywhere? We could change and clean up some parts.

Il mer 22 gen 2020, 16:35 Jonah Graham <[hidden email]> ha scritto:
> This issue will be an item in next week's CDT monthly call

That should have said next month's CDT monthly call. Details/agenda coming soon.

Thanks
Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 22 Jan 2020 at 10:15, Jonah Graham <[hidden email]> wrote:
Hello folks,

This June it will be 4 years since the last major version of CDT was released (change from 8.x to 9.0). During that upgrade it was possible for the first time since 2011 to introduce a breaking API change.

There has been a lot of discussions recently on parts of CDT that are no longer maintained, working or otherwise useful. So it is now time to start preparing for the next version upgrade and to give us a chance to reconcile, internalize, deprecate or remove API and features that are no longer fit for purpose and/or maintained.

To give everyone some background, this was the 9.0 live planning document and the end result was a large API section in the N&N that explains all API changes. 

This email is part of the beginning of that process so please feel free to comment. This issue will be an item in next week's CDT monthly call - stay tuned for an email about that.

Thanks,
Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev


--
Alexander Kurtakov
Red Hat Eclipse Team

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev

_______________________________________________
cdt-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cdt-dev