[racket] deprecating planet version using para. in planet description?

There is certainly no rush for anyone to move to the new package system. We
appreciate it when people try things out and let us know, but a careful,
slow approach is totally fine. We plan to support the current planet system
(at the level its been getting anyways) for a long time (just as we still
support some very old apis at the library level) and there are lots of
things that we already know need improvement in the package system so it
isn't like we're waiting for people to help us fill up to-do lists or
anything like that, either. :)

Robby


On Fri, Dec 6, 2013 at 1:47 AM, Laurent <laurent.orseau at gmail.com> wrote:

> As an excuse for my complete oversight of this matter, I could say that
> it's a bit too early to mark my old-PLaneT packages as deprecated, since my
> new-PLaneT packages are mostly not yet supported by the current Racket
> release (single-collection).
>
> Laurent
>
>
> On Thu, Dec 5, 2013 at 7:27 PM, John Clements <clements at brinckerhoff.org>wrote:
>
>> It looks to me like the easiest way to mark a PLaneT version of some code
>> as deprecated in favor of a package version (as e.g. rsound) is to add a
>> paragraph to the description metadata on the PLaneT website.  I've done
>> this for a few of my packages, but as I don't see anyone else doing it, I
>> wanted to check and see whether there was general agreement on a different
>> mechanism.
>>
>> Thanks!
>>
>> John
>>
>>
>> ____________________
>>   Racket Users list:
>>   http://lists.racket-lang.org/users
>>
>
>
> ____________________
>   Racket Users list:
>   http://lists.racket-lang.org/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20131206/16c2a2c7/attachment.html>