[eclipse-pmc] Update of API Removal Process

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

Dear PMC colleagues

Here are the proposed changes to our
 API
Removal Process as per our discussion:

> Announce the upcoming deletion
on relevant mailing lists, including a link to the bug for community comment
(at least cross-project-issues-dev and eclipse-dev). 
Announce the upcoming deletion on all
relevant mailing lists, including a link to the bug for community comment
(at least cross-project-issues-dev, eclipse.org-committers@xxxxxxxxxxx
and eclipse-dev). 
QUESTION:
should we also send a note to eclipse.org-planning-council?

> Assuming no community disagreement,
update deprecation comment and add an entry in porting guide. The deprecation
comment and porting guide entry must also include a link to the bug report
to allow for further feedback 
> from API adopters. 
If there is no
community disagreement, annotate
all APIs that are to be removed with @noreference,
update the deprecation comment, and add an entry in
the porting guide. The deprecation
comment and porting guide entry must  explain
how to adapt the client code
and include a link to the bug report to allow for further feedback from
API adopters.

> After the required waiting period
has gone by, the API is removed and the porting guide entry is moved from
the "upcoming deletions" to the "deleted API" section
in the documentation. 
After the required waiting period has
gone by, the API is removed and the porting guide entry is moved from the
"Planned API removals"
to the "Removed
APIs" section in the documentation.



Once you approve those changes I will
make the corresponding updates to our Deprecation
Policy document as well. I will
also adjust the section about bundle and package versions according to
our last discussion i.e. decide case-by-case whether to increase the major
or minor version.

Dani