Smalltalk › Squeak › Squeak - Dev

Let's do it: deprecation

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Tobias Pape

Let's do it: deprecation

Hi all

so, there are now 5 Deprecation packages in the image,
for 3.9, 3.11, 4.5, 4.6, and 5.1. I'd say, lets

a) get rid of the 3.9 and 3.11 ones now, and
b) get rid of the 4.5 one after releasing 5.1 and
c) get rid of the 4.6 one after releasing 5.2 and
d) get rid of the 5.1 one after releasing 5.3 and so on.

So, how would we achieve a)? a Script to the Squeak-Version package?

Best regards
-Tobias

Bert Freudenberg

Re: Let's do it: deprecation

> On 08.10.2015, at 12:06, Tobias Pape <[hidden email]> wrote:
>
> Hi all
>
> so, there are now 5 Deprecation packages in the image,
> for 3.9, 3.11, 4.5, 4.6, and 5.1. I'd say, lets
>
> a) get rid of the 3.9 and 3.11 ones now, and
> b) get rid of the 4.5 one after releasing 5.1 and
> c) get rid of the 4.6 one after releasing 5.2 and
> d) get rid of the 5.1 one after releasing 5.3 and so on.
>
> So, how would we achieve a)? a Script to the Squeak-Version package?

Squeak-Version seems to be the right place, yes.

- Bert -

smime.p7s (5K) Download Attachment

Levente Uzonyi-2

Re: Let's do it: deprecation

In reply to this post by Tobias Pape

Hi Tobias,

We should decide whether we want to replace SharedQueue with SharedQueue2
before removing the latter's deprecated methods, because those are
intended to be present in the image during the migration in order to make
it easier. Without those methods one would have to reintroduce them, or
find another way to migrate.

Levente

On Thu, 8 Oct 2015, Tobias Pape wrote:

> Hi all
>
> so, there are now 5 Deprecation packages in the image,
> for 3.9, 3.11, 4.5, 4.6, and 5.1. I'd say, lets
>
> a) get rid of the 3.9 and 3.11 ones now, and
> b) get rid of the 4.5 one after releasing 5.1 and
> c) get rid of the 4.6 one after releasing 5.2 and
> d) get rid of the 5.1 one after releasing 5.3 and so on.
>
> So, how would we achieve a)? a Script to the Squeak-Version package?
>
> Best regards
> -Tobias
>
>

Tobias Pape

Re: Let's do it: deprecation

On 08.10.2015, at 21:54, Levente Uzonyi <[hidden email]> wrote:

> Hi Tobias,
>
> We should decide whether we want to replace SharedQueue with SharedQueue2 before removing the latter's deprecated methods, because those are intended to be present in the image during the migration in order to make it easier. Without those methods one would have to reintroduce them, or find another way to migrate.

Where are those?

Levente Uzonyi-2

Re: Let's do it: deprecation

They are in 39Deprecated: #flush and #flushAllSuchThat:.

Levente

On Thu, 8 Oct 2015, Tobias Pape wrote:

>
> On 08.10.2015, at 21:54, Levente Uzonyi <[hidden email]> wrote:
>
>> Hi Tobias,
>>
>> We should decide whether we want to replace SharedQueue with SharedQueue2 before removing the latter's deprecated methods, because those are intended to be present in the image during the migration in order to make it easier. Without those methods one would have to reintroduce them, or find another way to migrate.
>
> Where are those?
>
>
>

Tobias Pape

Re: Let's do it: deprecation

On 08.10.2015, at 22:10, Levente Uzonyi <[hidden email]> wrote:

> They are in 39Deprecated: #flush and #flushAllSuchThat:.

Well, if we cannot actually deprecate them, lest de-deprecate (precate???) them again?
Nobody's going to say 'I depended on them being removed' ;)

Best regards
-Tobias

>
> Levente
>
> On Thu, 8 Oct 2015, Tobias Pape wrote:
>
>>
>> On 08.10.2015, at 21:54, Levente Uzonyi <[hidden email]> wrote:
>>
>>> Hi Tobias,
>>>
>>> We should decide whether we want to replace SharedQueue with SharedQueue2 before removing the latter's deprecated methods, because those are intended to be present in the image during the migration in order to make it easier. Without those methods one would have to reintroduce them, or find another way to migrate.
>>
>> Where are those?