> There is even 8 tickets older than one year waiting for review.
>
> I don't know if they are a problem or not. They will make harder to find
> "real" todo-lists -- but then, who is going to go throught wishlists in any
> case?
I also occasionally go through old tickets, complaining internally
ab
On Mon, Jan 4, 2016 at 10:21 AM, kcrisman wrote:
> Thank you Jonathan for clarifying what I thought was obvious in what I was
> saying.
>
>
>> > As stated, that would break the compatibility with SMC magics that
>> William
>> > just declared intangible (and always "cell magic").
>>
>> Just to be
Thank you Jonathan for clarifying what I thought was obvious in what I was
saying.
> > As stated, that would break the compatibility with SMC magics that
> William
> > just declared intangible (and always "cell magic").
>
> Just to be clear: I don't care whether or not whatever design you
On Mon, 4 Jan 2016, Daniel Krenn wrote:
what is the plan for/status of - - The last activity there is 10 (and 7)
month ago.
It is not at all uncommon for a ticket to be forgotten. At
http://trac.sagemath.org/report/58 you will see a big list of those. As a
trivial example, two weeks ago I su
On 2016-01-04 18:14, Nathann Cohen wrote:
>> what is the plan for/status of http://trac.sagemath.org/ticket/16137
>> (and related tickets, e.g.
>> http://trac.sagemath.org/ticket/16107 ) ?
>> The last activity there is 10 (and 7) month ago.
>
> The technical terminology is "forgotten".
:)
> Why
> what is the plan for/status of http://trac.sagemath.org/ticket/16137
> (and related tickets, e.g.
> http://trac.sagemath.org/ticket/16107 ) ?
> The last activity there is 10 (and 7) month ago.
The technical terminology is "forgotten".
Why don't you ask on the tickets directly, so that the guys
Dear all,
what is the plan for/status of http://trac.sagemath.org/ticket/16137
(and related tickets, e.g.
http://trac.sagemath.org/ticket/16107 ) ?
The last activity there is 10 (and 7) month ago.
Best, Daniel
--
You received this message because you are subscribed to the Google Groups
"sage-d
Hi,
I confirm that the patchbot hera-OptiPlex-7010 misbehaves: it
systematically returns "build failed" with the message
The content of "/home/hera/sage-patchbot/build/pkgs/r_jupyter/type" must be
'base', 'standard', 'optional', 'experimental' or 'pip'
Apply -- 4 seconds
Traceback (most recent
