for Thursday, November 19th. Yesterday, 859 open tickets. Today, 861 open tickets. That's not the direction that we want to go, folks. ;-) -- Marshall
for Thursday, November 19th. Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Lots of activity on the bug list (20-30 tickets created/changed/closed) yesterday, but the total count is still going up.... -- Marshall There are still 96 active tickets with a milestone (as in 'to be fixed in') of Boost 1.36.0 https://svn.boost.org/trac/boost/milestone/Boost%201.36.0 I will be looking at #2115 today.
On Nov 20, 2009, at 9:11 AM, troy d. straszheim wrote:
Marshall Clow wrote:
for Thursday, November 19th. Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets.
Random question: do you close tickets when the fix arrives on the release branch, or when they hit the trunk?
I close tickets when the fix arrives on the release branch; but that's so I don't forget to merge across. I don't think we have a general policy on that. -- Marshall (who has fixed bugs and forgotten to merge to release before - and been embarrassed about it)
On Fri, Nov 20, 2009 at 09:27:05AM -0800, Marshall Clow wrote:
On Nov 20, 2009, at 9:11 AM, troy d. straszheim wrote:
Marshall Clow wrote:
for Thursday, November 19th. Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets.
Random question: do you close tickets when the fix arrives on the release branch, or when they hit the trunk?
I close tickets when the fix arrives on the release branch; but that's so I don't forget to merge across. I don't think we have a general policy on that.
From the point of view of a user, that would be a very good policy to put in place. I've tracked many bugs in the past that were fixed and closed, but only on trunk (and remained so across 1 or more releases). Thanks, -Steve
for Saturday, Nov 21 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Good job, people! Lets keep this going.... -- Marshall There are still 96 active tickets with a milestone (as in 'to be fixed in') of Boost 1.36.0 https://svn.boost.org/trac/boost/milestone/Boost%201.36.0 and 45 active tickets with a milestone (as in 'to be fixed in') of Boost 1.37.0 https://svn.boost.org/trac/boost/milestone/Boost%201.37.0
for Sunday, Nov 22 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Lets keep the ball rolling.... Here are the top 10 components by "Open ticket count" https://svn.boost.org/trac/boost/report/19 thread 62 date_time 48 test 41 iostreams 40 Python 37 quickbook 33 mpl 30 smart_ptr 30 asio 28 filesystem 28 That's 377 of the 849 open tickets right there. -- Marshall
Marshall Clow wrote:
for Sunday, Nov 22
Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets.
Lets keep the ball rolling....
Marshall, while I have no idea if more detailed reports are possible/easy using Trac, it seems to me that the reporting style above does not effectively encourage individual contribution. A report with top bug fixers, or report with deltas per component would show one's effort more prominently. - Volodya
for Monday, Nov 23 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 22: 828 open tickets. Way to go, people! Keep up the good work.. -- Marshall
for Tuesday, Nov 24 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. A few tickets re-opened, a few new ones. For those who want just to count bugs: Nov 24: 516 open bugs -- Marshall
On Nov 24, 2009, at 8:16 AM, John Maddock wrote:
A few tickets re-opened, a few new ones.
Sorry about that... been busy reopening Boost.Integer issues... the count should go back down again soon though...
Don't be sorry about it! If they're real bugs (and they're not fixed), they should be in tickets. The goal here is to fix bugs. Counting the number of open tickets is a (hopefully accurate) way of measuring that, but it is not (quite) the same. -- Marshall
for Wednesday, November 25 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. Nov 25: 827 open tickets. Back to moving in the right direction! For those who want just to count bugs: Nov 24: 516 open bugs Nov 25: 511 open bugs -- Marshall
for Thursday, November 26 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. Nov 25: 827 open tickets. Nov 26: 834 open tickets. Oops - heading back up..... For those who want just to count bugs: Nov 24: 516 open bugs Nov 25: 511 open bugs Nov 26: 514 open bugs -- Marshall
for Friday, November 27 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. Nov 25: 827 open tickets. Nov 26: 834 open tickets. Nov 27: 828 open tickets. That's more like it... heading down again. For those who want just to count bugs: Nov 24: 516 open bugs Nov 25: 511 open bugs Nov 26: 514 open bugs Nov 27: 510 open bugs -- Marshall
for Sunday, November 29 (Sorry about the lack of report yesterday; I was out having a life ;-)) Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. Nov 25: 827 open tickets. Nov 26: 834 open tickets. Nov 27: 828 open tickets. Nov 29: 819 open tickets. Still heading down - that's good! For those who want just to count bugs: Nov 24: 516 open bugs Nov 25: 511 open bugs Nov 26: 514 open bugs Nov 27: 510 open bugs Nov 29: 503 open bugs The bug sprint ends today. Can we finish with less than 500 open bugs? I've created a new report: Open Bugs count by Component: https://svn.boost.org/trac/boost/report/24 -- Marshall
Marshall Clow-2 wrote:
The bug sprint ends today. Can we finish with less than 500 open bugs?
I've created a new report: Open Bugs count by Component: https://svn.boost.org/trac/boost/report/24
-- Marshall
Thanks Marshall. I've created some new reports: {25} Open Patches count by Component : https://svn.boost.org/trac/boost/report/25 {26} Open Feature Requests count by Component : https://svn.boost.org/trac/boost/report/26 {27} Open Tasks count by Component : https://svn.boost.org/trac/boost/report/27 {28} Open Support Requests count by Component : https://svn.boost.org/trac/boost/report/28 {29} Active Showstoppers : https://svn.boost.org/trac/boost/report/29 {30} Active Regressions ; : https://svn.boost.org/trac/boost/report/30) There are 28 Showstoppers and 15 Regressions. It would be a great to decrease this number for the next Bug Sprint. HTH, Vicente -- View this message in context: http://old.nabble.com/Status-of-the-bug-sprint....-tp26430336p26566099.html Sent from the Boost - Dev mailing list archive at Nabble.com.
On Nov 29, 2009, at 1:06 PM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
The bug sprint ends today. Can we finish with less than 500 open bugs?
I've created a new report: Open Bugs count by Component: https://svn.boost.org/trac/boost/report/24
-- Marshall
Thanks Marshall.
I've created some new reports:
{25} Open Patches count by Component : https://svn.boost.org/trac/boost/report/25 {26} Open Feature Requests count by Component : https://svn.boost.org/trac/boost/report/26 {27} Open Tasks count by Component : https://svn.boost.org/trac/boost/report/27 {28} Open Support Requests count by Component : https://svn.boost.org/trac/boost/report/28 {29} Active Showstoppers : https://svn.boost.org/trac/boost/report/29 {30} Active Regressions ; : https://svn.boost.org/trac/boost/report/30)
There are 28 Showstoppers and 15 Regressions. It would be a great to decrease this number for the next Bug Sprint.
Very nice! IMHO, bugs that are marked as "showstoppers" should be dealt with before a release. (If you can release with open "showstopper"s, then they didn't stop the show, did they?) -- Marshall
Marshall Clow-2 wrote:
On Nov 29, 2009, at 1:06 PM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
The bug sprint ends today. Can we finish with less than 500 open bugs?
I've created a new report: Open Bugs count by Component: https://svn.boost.org/trac/boost/report/24
-- Marshall
Thanks Marshall.
I've created some new reports:
{25} Open Patches count by Component : https://svn.boost.org/trac/boost/report/25 {26} Open Feature Requests count by Component : https://svn.boost.org/trac/boost/report/26 {27} Open Tasks count by Component : https://svn.boost.org/trac/boost/report/27 {28} Open Support Requests count by Component : https://svn.boost.org/trac/boost/report/28 {29} Active Showstoppers : https://svn.boost.org/trac/boost/report/29 {30} Active Regressions ; : https://svn.boost.org/trac/boost/report/30)
There are 28 Showstoppers and 15 Regressions. It would be a great to decrease this number for the next Bug Sprint.
Very nice!
IMHO, bugs that are marked as "showstoppers" should be dealt with before a release. (If you can release with open "showstopper"s, then they didn't stop the show, did they?)
-- Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
I'll be less ambitious, what about requesting less that 15 Showstoppers and less than 7 Regressions for the next release, 1.42? We could decrease to 7-4 for 1.43 and finally 0-0 for 1.44. Best, Vicente -- View this message in context: http://old.nabble.com/Status-of-the-bug-sprint....-tp26430336p26568619.html Sent from the Boost - Dev mailing list archive at Nabble.com.
for Monday, November 30 Nov 18: 859 open tickets. Nov 19: 861 open tickets. Nov 20: 862 open tickets. Nov 21: 849 open tickets. Nov 22: 849 open tickets. Nov 23: 828 open tickets. Nov 24: 836 open tickets. Nov 25: 827 open tickets. Nov 26: 834 open tickets. Nov 27: 828 open tickets. Nov 29: 819 open tickets. Nov 30: 818 open tickets. For those who want just to count bugs: Nov 24: 516 open bugs Nov 25: 511 open bugs Nov 26: 514 open bugs Nov 27: 510 open bugs Nov 29: 503 open bugs Nov 30: 502 open bugs The bug sprint is now over. (Of course, that doesn't mean you can't keep fixing bugs!) Thanks to all that participated. We knocked off about 5% of the open tickets. -- Marshall
Hi, Marshall Clow-2 wrote:
for Thursday, November 19th.
Yesterday, 859 open tickets. Today, 861 open tickets.
That's not the direction that we want to go, folks. ;-)
For the Bug sprint I would like to see reduced the number of bugs. This do not means that the other are not important. We have a problem because Patches could concern Bugs or feature requests. I purpose to Move all the patches to the corresponding category and add a new field to state if there is a patch available or not. Could you provide a query reports of the number of bugs by component, number of patches by component, ... I would like we try also to reduce the number of bugs by library. Why not having as goal that no library has more than 30 bugs? Here they are the libraries having more than 30 tickets: thread 62 date_time 48 iostreams 40 test 40 Python 39 Do the concerned authors agree to try to reduce these figures? Best, Vicente -- View this message in context: http://old.nabble.com/Status-of-the-bug-sprint....-tp26430336p26456028.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Marshall Clow-2 wrote:
for Thursday, November 19th.
Yesterday, 859 open tickets. Today, 861 open tickets.
That's not the direction that we want to go, folks. ;-)
Who should set the milestone of a ticket? the reporter or any to state when the ticket is expected to be solved or the author to state when s/he expect to solve the issue? Regards, Vicente -- View this message in context: http://old.nabble.com/Status-of-the-bug-sprint....-tp26430336p26456175.html Sent from the Boost - Dev mailing list archive at Nabble.com.
On Nov 21, 2009, at 4:35 AM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
for Thursday, November 19th.
Yesterday, 859 open tickets. Today, 861 open tickets.
That's not the direction that we want to go, folks. ;-)
Who should set the milestone of a ticket? the reporter or any to state when the ticket is expected to be solved or the author to state when s/he expect to solve the issue?
The latter. -- Marshall
2009/11/21 Marshall Clow <mclow.lists@gmail.com>:
Who should set the milestone of a ticket? the reporter or any to state when the ticket is expected to be solved or the author to state when s/he expect to solve the issue?
The latter.
Most people don't bother. You're best of ignoring the milestone altogether. Daniel
Marshall Clow-2 wrote:
On Nov 21, 2009, at 4:35 AM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
for Thursday, November 19th.
Yesterday, 859 open tickets. Today, 861 open tickets.
That's not the direction that we want to go, folks. ;-)
Who should set the milestone of a ticket? the reporter or any to state when the ticket is expected to be solved or the author to state when s/he expect to solve the issue?
The latter.
-- Marshall
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Then thre is no sens to have Milestone for 1.41 or before, isn't it? Vicente -- View this message in context: http://old.nabble.com/Status-of-the-bug-sprint....-tp26430336p26461541.html Sent from the Boost - Dev mailing list archive at Nabble.com.
On Nov 21, 2009, at 3:42 PM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
On Nov 21, 2009, at 4:35 AM, Vicente Botet Escriba wrote:
Marshall Clow-2 wrote:
for Thursday, November 19th.
Yesterday, 859 open tickets. Today, 861 open tickets.
That's not the direction that we want to go, folks. ;-)
Who should set the milestone of a ticket? the reporter or any to state when the ticket is expected to be solved or the author to state when s/he expect to solve the issue?
The latter.
-- Marshall
Then thre is no sens to have Milestone for 1.41 or before, isn't it? Vicente
It means that somehow, in the past, someone expected that the bug would be fixed in the 1.36 (say) release, but it hasn't been fixed yet. -- Marshall P.S. I'm encouraging people to look at those bugs because they've been around for a long time.....
participants (7)
-
Daniel James -
John Maddock -
Marshall Clow -
Steve M. Robbins -
troy d. straszheim -
Vicente Botet Escriba -
Vladimir Prus