On Aug 20, 8:05 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>

Hello,

> I propose that the next SAGE bug squash even be Saturday, September 1, which 
> is
> in two weeks.   Whose interested?

I am. Date is fine, Saturday is also a good day because it lets one
recover on Sunday.

How does this relate to the 2.8.3 release date? I have started
triaging potentially interesting bugs to be fixed for the 2.8.3
milestone. While I haven't gotten as far as I would like yet I would
really like somebody with detailed knowledge of the notebook to go
through the open notebook bugs and decide which have been fixed and
which are still relevant. At Bug Day 1 the notebook got very little
love & tender care, but there are plenty of tickets that are notebook
related.

While we are milestones: Do you have any thoughts on 3.0 regrading
features and timing? I think it would also be great if the patches
that went to referees would also go into trac as a ticket, that way
interested parties know what is coming up.

>
> It might be fun for the Seattle-area people to all meet up in a common
> location for this.

Love to join you, but my commute is a bitch :)

I am about to finish the summary of Bug Day 1 and I have put a
preliminary version at http://www.sagemath.org:9001/bug1/Results - the
biggest lesson I have learned from Bug Day 1 is to report the results
in real time because if you have to go through a log with a couple
thousand lines after the fact it is a little more work than hoped for.

Cheers,

Michael

>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://www.williamstein.org


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to