[Bug Sprint] Status for Monday, November 29th
There were 37 changes to the trac database yesterday. [ I'd like to say "37 tickets were changed", but some tickets were changed more than once. ] A couple of notes: 1) Please log into the Trac system before you add/modify a ticket. "Anonymous said:" is hard to follow up. 2) It is perfectly OK to add a comment to a ticket that says "I tested this patch on my system (foo, gcc 1.2.3.4, etc) and it worked fine/didn't work/etc" General information about the bug sprint is here: https://svn.boost.org/trac/boost/wiki/BugSprintNov2010 General information about how the Trac system works is here: https://svn.boost.org/trac/boost/wiki/TicketWorkflow Overall bug count: November 26: 946 November 27: 939 November 28: 930 November 29: 934 (whoops, that's the wrong direction!) Activities on the trac system yesterday: anonymous 11 mikhailberis 10 viboes 5 ktchan 4 --others- 7 Useful reports: https://svn.boost.org/trac/boost/report/1 -- full list of tickets https://svn.boost.org/trac/boost/report/18 -- ticket counts by owner https://svn.boost.org/trac/boost/report/19 -- ticket counts by component https://svn.boost.org/trac/boost/report/20 -- ticket counts by ticket type https://svn.boost.org/trac/boost/report/21 -- ticket counts by milestone
Hi, There are 3 tickets related to CMAKE. As CMAKE is not part of Boost yet I propose we close these tickets. Ticket Summary Component Status Created Modified #2044 windows debug popups in build slave mode CMake assigned 2 years 12 months #3667 linking debug builds CMake new 12 months 12 months #3757 BUILD_BOOST_WSERIALIZATION is ignored. CMake new 12 months 12 months Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/Bug-Sprint-Status-for-Monday-November-29t... Sent from the Boost - Dev mailing list archive at Nabble.com.
On 1:59 PM, Marshall Clow wrote:
There were 37 changes to the trac database yesterday.
Thanks for keeping us updated! As well as the ticket activity, I'd love to hear about commits to the trunk, too. That's where the rubber meets the road.
[...] 2) It is perfectly OK to add a comment to a ticket that says "I tested this patch on my system (foo, gcc 1.2.3.4, etc) and it worked fine/didn't work/etc"
Excellent. (In fact, I'd encourage this as strongly as possible. Anyone trying a patch to weigh in either way, including that the patch couldn't be applied because the trunk has diverged.) And tickets that have been given this treatment: how are sprinters keeping track of them? They deserve special status to commit-ers, don't they?
Hopefully that means that more yellow is going green on the regression matrix!
On Mon, Nov 29, 2010 at 9:25 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
1) Please log into the Trac system before you add/modify a ticket. "Anonymous said:" is hard to follow up
If you're in a hurry, typing your username in the "Your email or username" field works just as well. Just don't forget it! Also, if you don't have a username, please, please, please enter your email. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Hi, I would like to request the people that are closing tickets as fixed to add the changeset reference so the we can understand what has been done, in addition an explanation of the resolution will be welcome. Seen a closed ticket just with the * Status changed from new to closed * Resolution set to fixed is discouraging for those that are following the ticket outcome. I understand that this will take you some more time, but this effort will save time for the whole Boost community. Best, Vicente -- View this message in context: http://boost.2283326.n4.nabble.com/Bug-Sprint-Status-for-Monday-November-29t... Sent from the Boost - Dev mailing list archive at Nabble.com.
participants (7)
-
Dave Abrahams -
Jeff Flinn -
Jim Bell -
KTC -
Marshall Clow -
Vicente Botet -
Vladimir Prus