On Sep 12, 1:22 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi,
<SNIP>
>
> the Sage development process demands that for changes, one opens a
> ticket in trac (it's as easy as 1-2-3 to get an account,
> seehttp://wiki.sagemath.org/TracGuidelines) then you or someone else
> provides a solution, e.g. a patch, then it gets reviewed. Upon
> positive review, the integrator(s) put them in the next release, which
> is tested in "alpha" and "rc" phases. (Somebody correct me if I'm
> wrong, thanks.)
>
> The current suboptimal situation is best explained by looking behind
> the thread "Reveiews, Reviews, Reviews for Sage 3.1.2.rc0" from Aug.
> 30th, the same day of your post.
>
> Since then, it only has become worse:
>
> - currently (see trac report {1} Active Tickets (910 matches)),
> there are all in all more than 900 tickets open, this number keeps
> growing over the last two weeks
At the start of the 3.1.2. cycle we were at 960 open tickets, so we
are making progress there. It is just that at the end of a cycle the
number of open tickets goes up since we only merge release critical
patches.
> - currently (see trac report {14}: Tickets needing review (by
> component) (51 matches)),
> more than 50 tickets in trac that have a patch attached, but they
> are waiting to be reviewed
> (that number was "down" to 40 two weeks ago)
It was well over 100 at the start of Dev1, so this is actually not too
bad at the moment. Considering the turnover 50 tickets to review is
pretty normal. What is bad is that certain tickets sit around
unreviewed for long times. But at review process is mandatory to keep
the quality up :)
> - currently (see trac report {12} Tickets with negative review /
> pending changes (28 matches)),
> almost 30 tickets have been reviewed, but not so positively --- more
> work is needed.
> This number kept rather constant for the last two weeks
>
> - currently (see trac report {11} Tickets with positive review (12
> matches)), there
> is a quick growing number of tickets with positive review, which
> only wait to be integrated
>
> So what did the Sage team do in the last two weeks? Well, the overall
> number of tickets in trac
> grew from below 4000 to more than 4100, so the above numbers refer not
> to the same tickets.
> There are big efforts ongoing, but for every ticket "slain", at least
> one (rather two) new arises ...
This is just business as usual, so no need to worry. The more users
you have the more bugs will be discovered. There will be a Sage
development days in January 2009 in San Diego where we will get
together and fix bugs all days, so heopfully then we will close some
long standing bugs.
> In the end, Sage is a community effort, and we both are part of the
> community.
> And I value your effort to bring the documentation to a more
> satisfactory state.
>
> So I just opened trac ticket #4107 for the issue of this thread.
Thanks.
> Now if you e.g. could apply your changes as patch file, that surely
> will not only help the reviewer,
> but also the integrator to do his work!
It would also be good if you did send the patch as an attachment. As
is it seems to be inline.
> Cheers,
> gsw
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
