The problem here is that some of these have assumptions which have never 
been met.
39Deprecated:
- ContextPart >> #methodSelector can be safely removed
- SharedQueue2 >> #flush and #flushAllSuchThat: can be removed, but that 
will make it incompatible with SharedQueue. The migration to SharedQueue2 
has not happened yet, so these methods have senders in the image (even if 
the receiver is not a SharedQueue2). And it's possible that we'll migrate 
to something else.
311Deprecated: Everything looks safe to be removed.
45Deprecated: Most methods seem to be safe to be removed.

Levente

On Sat, 2 May 2015, Tobias Pape wrote:

>
> On 02.05.2015, at 15:07, David T. Lewis <lewis at mail.msen.com> wrote:
>
>> On Fri, May 01, 2015 at 05:23:15AM -0700, Marcel Taeumel wrote:
>>> Hi ---
>>>
>>> We should unload all historic deprecations... and focus on what is needed
>>> for 46Deprecated (if it cannot be deleted).
>>>
>>
>> It might be better to do this immediately after the next release, rather than
>> before. Removing things can have unintended side effects, so it is good to do
>> it earlier in the release cycle.
>
> Those things (39 and 311) have been deprecated for long, so I'd rather
> say to lose them right before and keep 45 around one more cycle…
> Best
> 	-Tobias
>
>
>
>