Re: [platform-swt-dev] SWT and deprecations

[Markus Keller <markus_keller@xxxxxxxxxx>]

The general answer to deprecation is "don't
do it".

For specific APIs, we need a compelling
reason as outlined in
https://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy

Note that deprecated APIs still have
to work as originally specified.
If an API is widely used and not clearly
broken, then we don't want to add work for clients (see e.g. Bug
411137).
Sometimes, the best solution is to add
a "Note: " paragraph instead of deprecating an API.
=> There is no general answer; it
all depends on the specific use case.

If you want to deprecate something,
then:
- open a bug where you describe your
arguments
- get a review from both
   - the component lead
   - the author or current
maintainer of the API (use Show Annotations)

HTH
Markus



From:      
 Aleksandar Kurtakov
<akurtako@xxxxxxxxxx>
To:      
 "Eclipse Platform
SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
Date:      
 2013-12-06 11:09
Subject:    
   [platform-swt-dev]
SWT and deprecations
Sent by:    
   platform-swt-dev-bounces@xxxxxxxxxxx

---

Regarding SWT deprecation policy.
Marking non-recomended methods as deprecated seems to be the right thing
to me. I know this one is really simple case but I'm looking for the general
discussion on the topic here. 
Deprecating things might introduce some inconvenience for users but if
something is not recomended we should make it obvious to them. This is
really important for paving the road ahead as we need to give enough time
for people to move ahead. Also helping people use the recommended way is
worth it by itself.
What others think ? 

Alexander Kurtakov
Red Hat Eclipse team

_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev