Vote on bugs to be fixed for sage-4.4 "stabilization release".

[William Stein]

Hi,

Lately it seems like Sage has gotten more bugs rather than less. I
think it's time for a stabilization release -- say Sage-4.4 -- that
fixes the absolutely most annoying of these bugs.

What are *your* top 4 bugs that are in sage-4.3.2 that you really wish
were fixed?? If you care, respond to this thread with a list of 4
bugs which *must* have corresponding trac tickets. We'll take the
most popular reported bugs, and the ones that aren't impossible will
all be upgraded to blockers and fixed for sage-4.4, which will be a
bug fix release.

My top 4:

1. Right now in the Sage notebook the cells lose focus in many situations:
http://trac.sagemath.org/sage_trac/ticket/8231

2. Defect: tab completion broken for many parent objects (new)
http://trac.sagemath.org/sage_trac/ticket/8223

3. Sage takes too long to startup still:
http://trac.sagemath.org/sage_trac/ticket/8254

4. %time broken in the notebook:
http://trac.sagemath.org/sage_trac/ticket/8225

PLEASE: No discussion about releases numbers, the GPL, etc., in this thread!

-- William

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

[Tom Boothby]

My top 1:

1) Defect: Handle interrupts better in the notebook
http://trac.sagemath.org/sage_trac/ticket/7702

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

[Marshall Hampton]

On Feb 12, 9:54 pm, Tom Boothby <tomas.boot...@gmail.com> wrote:
> My top 1:
>
> 1) Defect: Handle interrupts better in the notebookhttp://trac.sagemath.org/sage_trac/ticket/7702

I'll second that, I think that's the bug that irritates me the most
right now.

-Marshall

[William Stein]

Hi,

I've created this trac wiki page with a subset of the 10 most
important current bug/issues in Sage, according to votes in this
thread:

http://trac.sagemath.org/sage_trac/wiki/stab1

These are all bugs/issues that many people care about. None are
highly specialized.

So if anybody has some time to donate to working on Sage, and you want
to make an impact that people will definitely appreciate, work on one
of the bugs listed at http://trac.sagemath.org/sage_trac/wiki/stab1

After seeing the actual bugs, I no longer see the wisdom of making a
specific release targeting them. The problem is that they are all
potentially hard, and there is no telling when they will all be
resolved. However, listing them all together and seeing that a lot of
people care about them will help encourage people to work on them.

As people make progress on any of these, feel free to respond to this
thread with an update.

It still makes sense to have the next Sage release be Sage-4.3.4.
Note that nobody has stepped up to be release manager yet, so that
release is currently *NOT* being made by anyone, even though if
somebody did the work, we could easily have an alpha in a day, as
there are 52 tickets with positive review right now:

http://trac.sagemath.org/sage_trac/report/11

A lot are in combinatorics and graph theory, so if somebody in the
sage-combinat group wants to be the release manager for sage-4.3.4,
that could make a lot of sense.

-- William