Discussion:
[cross-project-issues-dev] Will the Platform Start Making Major Version Increments?
Ed Merks
2018-10-30 10:33:40 UTC
Permalink
FYI,

It was brought to my attention that the platform team apparently plans
to make major version increments when deleting deprecated API:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=540481#c5

I think this will simply be a *major disaster for the ecosystem*.   How
many highly stable plugins will not be installable in the next release? 
Many thousands!  What do all the API consumers need to do?  Bump their
upper bound; presumably they've all be paying close attention and have
stopped using the deprecated APIs long ago...

I'm starting to feel ill just considering inflicting such a thing on the
community.

I would have expected to see some announcement on such a policy change.
*I beg the Eclipse PMC to reconsider.*  I'll quickly resort to ugly
threats if necessary.  I.e., I will not change the version ranges in EMF
and I will not provide a build for 2018-12 if this ill conceived plan
goes forward, which of course means 2018-12 itself will not go forward.

I find it inconceivable that anyone thinks this will be anything but a
complete and total disaster.

Regards,
Ed
Daniel Megert
2018-10-30 15:29:07 UTC
Permalink
Hi Ed

Last time we discussed this in 2017 there were different opinions on this
topic but we never decided on the topic. Today we decided unanimously that
in general we will NOT increase the major version when removing deprecated
API.

HTH
Dani



From: Ed Merks <***@gmail.com>
To: Cross project issues <cross-project-issues-***@eclipse.org>
Date: 30.10.2018 11:33
Subject: [cross-project-issues-dev] Will the Platform Start Making
Major Version Increments?
Sent by: cross-project-issues-dev-***@eclipse.org



FYI,
It was brought to my attention that the platform team apparently plans to
make major version increments when deleting deprecated API:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=540481#c5
I think this will simply be a major disaster for the ecosystem. How many
highly stable plugins will not be installable in the next release? Many
thousands! What do all the API consumers need to do? Bump their upper
bound; presumably they've all be paying close attention and have stopped
using the deprecated APIs long ago...
I'm starting to feel ill just considering inflicting such a thing on the
community.
I would have expected to see some announcement on such a policy change. I
beg the Eclipse PMC to reconsider. I'll quickly resort to ugly threats if
necessary. I.e., I will not change the version ranges in EMF and I will
not provide a build for 2018-12 if this ill conceived plan goes forward,
which of course means 2018-12 itself will not go forward.
I find it inconceivable that anyone thinks this will be anything but a
complete and total disaster.
Regards,
Ed_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Ed Merks
2018-10-30 16:01:22 UTC
Permalink
Dani,

My faith is restored! Thanks!!

Regards,
Ed
Post by Daniel Megert
Hi Ed
Last time we discussed this in 2017 there were different opinions on
this topic but we never decided on the topic. Today we decided
unanimously that in general we will NOT increase the major version
when removing deprecated API.
HTH
Dani
Date: 30.10.2018 11:33
Subject: [cross-project-issues-dev] Will the Platform Start Making
Major        Version Increments?
------------------------------------------------------------------------
FYI,
It was brought to my attention that the platform team apparently plans
_https://bugs.eclipse.org/bugs/show_bug.cgi?id=540481#c5_
I think this will simply be a *major disaster for the ecosystem*.  
How many highly stable plugins will not be installable in the next
release?  Many thousands! What do all the API consumers need to do? 
Bump their upper bound; presumably they've all be paying close
attention and have stopped using the deprecated APIs long ago...
I'm starting to feel ill just considering inflicting such a thing on
the community.
I would have expected to see some announcement on such a policy
change. *I beg the Eclipse PMC to reconsider.* I'll quickly resort to
ugly threats if necessary.  I.e., I will not change the version ranges
in EMF and I will not provide a build for 2018-12 if this ill
conceived plan goes forward, which of course means 2018-12 itself will
not go forward.
I find it inconceivable that anyone thinks this will be anything but a
complete and total disaster.
Regards,
Ed_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Matthias Sohn
2018-10-30 23:57:33 UTC
Permalink
Post by Daniel Megert
Hi Ed
Last time we discussed this in 2017 there were different opinions on this
topic but we never decided on the topic. Today we decided unanimously that
in general we will NOT increase the major version when removing deprecated
API.
HTH
Dani
+1, thanks for this decision
Post by Daniel Megert
Date: 30.10.2018 11:33
Subject: [cross-project-issues-dev] Will the Platform Start Making
Major Version Increments?
------------------------------
FYI,
It was brought to my attention that the platform team apparently plans to
*https://bugs.eclipse.org/bugs/show_bug.cgi?id=540481#c5*
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=540481#c5>
I think this will simply be a *major disaster for the ecosystem*. How
many highly stable plugins will not be installable in the next release?
Many thousands! What do all the API consumers need to do? Bump their
upper bound; presumably they've all be paying close attention and have
stopped using the deprecated APIs long ago...
I'm starting to feel ill just considering inflicting such a thing on the
community.
I would have expected to see some announcement on such a policy change. *I
beg the Eclipse PMC to reconsider.* I'll quickly resort to ugly threats
if necessary. I.e., I will not change the version ranges in EMF and I will
not provide a build for 2018-12 if this ill conceived plan goes forward,
which of course means 2018-12 itself will not go forward.
I find it inconceivable that anyone thinks this will be anything but a
complete and total disaster.
Regards,
Ed_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
David Williams
2018-11-07 03:29:23 UTC
Permalink
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-***@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
Loading...