Second call: The Boost Bug Sprint is coming!!
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th. The goal is to address a large number of open bugs/patches/feature requests in the Trac system at <http://svn.boost.org/trac/report/1>. There are currently 791 open tickets; we'd like to knock that number down _a lot_. What can you do? 1) You can fix bugs. * If you are a library maintainer, you can commit your fixes. ;-) * If you are not a library maintainer, you can fix a problem on your local machine (and test it!!), and then attach your fix as a patch to the Trac ticket for the library maintainer to commit. If you do this, please provide a test case that exercises the problem; i.e, one that fails w/o your patch, and succeeds afterwards. 2) You can characterize bugs. * You can attempt to replicate the bug on your system(s), and attach information that you discover to the Trac ticket. This will make it easier for other people to solve the problem, even if you cannot. * You can write test cases demonstrating the problem, and attach them to the Trac ticket. * You can determine if the bug still exists; sometimes they get fixed, and the ticket never gets closed. In this case, try to identify a checkin that addresses the bug; it's always suspicious when bugs go away "by accident." 3) You can test patches. * Some of the tickets in the Trac system contain patches - some are quite old. You can install these patches on your system, and determine if they (a) build, and (b) work. * You can write test cases for the patches, and attach them to the ticket. 4) You can help implement new features. * There are a whole set of "feature requests" in the Trac system. If you have an idea about one of these, you can add comments to the Trac system. You can attempt to implement these new features, and attach the patch to the ticket. (Don't forget the test cases!!). Every day during the bug sprint, I'll post the # of tickets modified/closed/opened on the previous day, as well as the total number of open tickets. --------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou@u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost@objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco@osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
AMDG Marshall Clow wrote:
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
I think that Friday is the 29th.
The goal is to address a large number of open bugs/patches/feature requests in the Trac system at <http://svn.boost.org/trac/report/1>. There are currently 791 open tickets; we'd like to knock that number down _a lot_.
What can you do?
Count me in. I'll just keep fixing bugs... I can also start running como regressions again if that would be helpful. I had to stop because it was taking up more resources than I could afford, but I think I can at least keep it running during the sprint. In Christ, Steven Watanabe
Hi, I would like to fix a bug or implement a feature requests for Boost.Thread. Does this has a sens if Anthony, the library maintainer do not participate to this Bug Sprint? Vicente ----- Original Message ----- From: "Marshall Clow" <marshall@idio.com> To: <boost@lists.boost.org> Sent: Tuesday, May 26, 2009 3:10 PM Subject: [boost] Second call: The Boost Bug Sprint is coming!!
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
The goal is to address a large number of open bugs/patches/feature requests in the Trac system at <http://svn.boost.org/trac/report/1>. There are currently 791 open tickets; we'd like to knock that number down _a lot_.
What can you do?
1) You can fix bugs. * If you are a library maintainer, you can commit your fixes. ;-) * If you are not a library maintainer, you can fix a problem on your local machine (and test it!!), and then attach your fix as a patch to the Trac ticket for the library maintainer to commit. If you do this, please provide a test case that exercises the problem; i.e, one that fails w/o your patch, and succeeds afterwards.
2) You can characterize bugs. * You can attempt to replicate the bug on your system(s), and attach information that you discover to the Trac ticket. This will make it easier for other people to solve the problem, even if you cannot. * You can write test cases demonstrating the problem, and attach them to the Trac ticket. * You can determine if the bug still exists; sometimes they get fixed, and the ticket never gets closed. In this case, try to identify a checkin that addresses the bug; it's always suspicious when bugs go away "by accident."
3) You can test patches. * Some of the tickets in the Trac system contain patches - some are quite old. You can install these patches on your system, and determine if they (a) build, and (b) work. * You can write test cases for the patches, and attach them to the ticket.
4) You can help implement new features. * There are a whole set of "feature requests" in the Trac system. If you have an idea about one of these, you can add comments to the Trac system. You can attempt to implement these new features, and attach the patch to the ticket. (Don't forget the test cases!!).
Every day during the bug sprint, I'll post the # of tickets modified/closed/opened on the previous day, as well as the total number of open tickets.
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou@u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost@objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco@osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4)
-- -- Marshall
Marshall Clow Idio Software <mailto:marshall@idio.com>
It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Wed, May 27, 2009 at 2:01 AM, vicente.botet <vicente.botet@wanadoo.fr>wrote:
Hi, I would like to fix a bug or implement a feature requests for Boost.Thread. Does this has a sens if Anthony, the library maintainer do not participate to this Bug Sprint?
Please don't top-post:-( As far as fixing bugs goes, please go ahead and submit your patch regardless of whether or not the maintainer for a library is signed up. We will pester maintainers with outstanding patches to apply/correct/reject as needed. Features might best be discussed first. At least for filesystem, I get a lot of feature requests that have hidden implications that would need to be resolved before moving forward. --Beman
Hi, I would like to fix a bug or implement a feature requests for Boost.Thread. Does this has a sens if Anthony, the library maintainer do not participate to this Bug Sprint?
Certainly. Even if Anthony is not participating in the Bug Sprint, you can fix bugs and/or implement new features. Just attach the patches to Trac tickets, and Anthony can merge them into the source base at a later date. I'll add you to the sign-up sheet. ;-) -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
Hi, ----- Original Message ----- From: "Marshall Clow" <marshall@idio.com> To: <boost@lists.boost.org> Sent: Wednesday, May 27, 2009 3:06 PM Subject: Re: [boost] Second call: The Boost Bug Sprint is coming!!
Hi, I would like to fix a bug or implement a feature requests for Boost.Thread. Does this has a sens if Anthony, the library maintainer do not participate to this Bug Sprint?
Certainly.
Even if Anthony is not participating in the Bug Sprint, you can fix bugs and/or implement new features. Just attach the patches to Trac tickets, and Anthony can merge them into the source base at a later date.
I'll add you to the sign-up sheet. ;-)
I have started with two tickets I submitted (https://svn.boost.org/trac/boost/ticket/2742, https://svn.boost.org/trac/boost/ticket/2739) I have tested them with cygwin gcc 3.4.6. Could someone take a look and test them on other platforms? Thanks, Vicente
Marshall Clow wrote:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou@u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost@objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco@osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4)
9) Daniel Wallin (parameter, ...) -- Daniel Wallin BoostPro Computing http://www.boostpro.com
Marshall Clow <marshall@idio.com> writes:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou@u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost@objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco@osl.iu.edu> (will test and commit graph patches) 7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4)
Anthony Williams (thread) Anthony -- Author of C++ Concurrency in Action | http://www.manning.com/williams just::thread C++0x thread library | http://www.stdthread.co.uk Just Software Solutions Ltd | http://www.justsoftwaresolutions.co.uk 15 Carrallack Mews, St Just, Cornwall, TR19 7UL, UK. Company No. 5478976
Anthony Williams <anthony.ajw <at> gmail.com> writes:
Marshall Clow <marshall <at> idio.com> writes:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou <at> u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost <at> objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco <at> osl.iu.edu> (will test and commit graph
patches)
7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4)
Anthony Williams (thread)
I am not saying I am committing ;o), but I 'll try to fix as many as possible in upcoming days. Gennadiy Rozental(test) P.S. Are we going to keep track of the progress? Like in a form "n out of m fixed..."
At 5:39 PM +0000 5/29/09, Gennadiy Rozental wrote:
Anthony Williams <anthony.ajw <at> gmail.com> writes:
Marshall Clow <marshall <at> idio.com> writes:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do. 1) Marshall Clow (coordination, Mac OS X characterization) 2) Beman Dawes (filesystem, system, timer) 3) Doug Gregor (function, graph, logic, mpi, numeric, property_map, signals) 4) "joel falcou" <joel.falcou <at> u-psud.fr> ( linux gcc testing/VC 2008 testing, patching) 5) Michael Caisse <boost <at> objectmodelingdesigns.com> (bug fixing) 6) Jeremiah Willcock <jewillco <at> osl.iu.edu> (will test and commit graph
patches)
7) David Abrahams (iterator, python) 8) Sohail Somani (patches for g++ 4.2.4)
Anthony Williams (thread)
I am not saying I am committing ;o), but I 'll try to fix as many as possible in upcoming days.
Great!
P.S. Are we going to keep track of the progress? Like in a form "n out of m fixed..."
Yes; I'm working on some scripts to generate summary and change reports. Here's a taste of the summary reports: Open Tickets by Ticket Type 495 Bugs 175 Feature Requests 2 Library Submissions 82 Patches 9 Support Requests 26 Tasks Open Tickets by Year Created 4 2001 1 2002 3 2003 3 2004 11 2005 27 2006 147 2007 328 2008 265 2009 [ Ouch - those eight tickets that are more than five years old (7 are feature requests) ] -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
AMDG Marshall Clow wrote:
Yes; I'm working on some scripts to generate summary and change reports. Here's a taste of the summary reports:
Open Tickets by Ticket Type 495 Bugs 175 Feature Requests 2 Library Submissions 82 Patches 9 Support Requests 26 Tasks
Open Tickets by Year Created 4 2001 1 2002 3 2003 3 2004 11 2005 27 2006 147 2007 328 2008 265 2009
[ Ouch - those eight tickets that are more than five years old (7 are feature requests) ]
Can we just close #100 and especially #182. No one is ever going to do anything with them. #145 was fixed at some point but was never closed. In Christ, Steven Watanabe
----- Original Message ----- From: "Steven Watanabe" <watanabesj@gmail.com> To: <boost@lists.boost.org> Sent: Saturday, May 30, 2009 12:44 AM Subject: Re: [boost] Second call: The Boost Bug Sprint is coming!!
Can we just close #100 and especially #182. No one is ever going to do anything with them.
I agree. What about #558 add database library Vicente
At 3:44 PM -0700 5/29/09, Steven Watanabe wrote:
AMDG
Marshall Clow wrote:
Yes; I'm working on some scripts to generate summary and change reports. Here's a taste of the summary reports:
Open Tickets by Ticket Type 495 Bugs 175 Feature Requests 2 Library Submissions 82 Patches 9 Support Requests 26 Tasks
Open Tickets by Year Created 4 2001 1 2002 3 2003 3 2004 11 2005 27 2006 147 2007 328 2008 265 2009
[ Ouch - those eight tickets that are more than five years old (7 are feature requests) ]
Can we just close #100 and especially #182. No one is ever going to do anything with them.
#145 was fixed at some point but was never closed.
Can someone who is familiar with date_time check #287? It looks to me like this patch was applied a while back, but the ticket was never closed. -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
I've started glancing at the tickets lists. Seem some have already patch with test and soem only patches. Is this process ok : 1/ Test patch and report ticket # if test passes so it can be closed 2/ write test for testless patches and goto 1 I think a few tickets can be tested/clsoed liek this and so we can jump onto tickets without patches.
I've started glancing at the tickets lists. Seem some have already patch with test and soem only patches.
Is this process ok : 1/ Test patch and report ticket # if test passes so it can be closed 2/ write test for testless patches and goto 1
I think a few tickets can be tested/clsoed liek this and so we can jump onto tickets without patches.
That would be great. If the test passes, note it in the ticket (along with your configuration). -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
Ticket #1384 (support request) has been sitting there for quite a while - might not be much use any more? -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
Vladimir Prus-3 wrote:
Richard Webb wrote:
Ticket #1384 (support request) has been sitting there for quite a while - might not be much use any more?
You might want to copy-paste the description of the ticket, since few people remember all ticket numbers.
- Volodya
It was opened 19 months ago by someone who was having problems linking with the date_time library in Visual C++ 2008 Express, and might be because 1.34 didn't have full VC9 support. In any case, i guess that the person who opened it isn't still waiting for an answer! -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
I am not saying I am committing ;o), but I 'll try to fix as many as possible in upcoming days.
Hi Gennadiy, please apply this small patch https://svn.boost.org/trac/boost/ticket/2647 thanks, Kevin
Marshall Clow wrote:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do.
I think this "committed" list is somewhat strange. I am not gonna commit to anything, but I've fixed a few bugs related to build system earlier today, and will probably do another pass later. - Volodya
At 9:45 PM +0400 5/29/09, Vladimir Prus wrote:
Marshall Clow wrote:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do.
I think this "committed" list is somewhat strange. I am not gonna commit to anything, but I've fixed a few bugs related to build system earlier today, and will probably do another pass later.
It's not as ominous as you are making out. "Committed" means that they have agreed to participate - that's all. They will be looking at trac tickets during the next 10 days. [ They may be doing other stuff (sleeping, etc ;-)), but they will spend some time looking at Trac tickets ] -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
Marshall Clow wrote:
At 9:45 PM +0400 5/29/09, Vladimir Prus wrote:
Marshall Clow wrote:
--------- Sign-up sheet -------- The following people have committed to participate in the bug sprint. Please add you name here, along with what you can do.
I think this "committed" list is somewhat strange. I am not gonna commit to anything, but I've fixed a few bugs related to build system earlier today, and will probably do another pass later.
It's not as ominous as you are making out.
It looks I'm not the only one scared by that world :-). BTW, it would be good if folks just the IRC channel for some socializing. IRC software is widely available and there's Chatzilla extension for firefox. Server is chat.freenode.net and channel is #boost. - Volodya
On 05/26/09 08:10, Marshall Clow wrote:
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
The goal is to address a large number of open bugs/patches/feature requests in the Trac system at <http://svn.boost.org/trac/report/1>. There are currently 791 open tickets; we'd like to knock that number down _a lot_.
What can you do?
[snip]
2) You can characterize bugs. * You can attempt to replicate the bug on your system(s), and attach information that you discover to the Trac ticket. [snip]
I'll participate. However, I just tried to add a test case for my system to: https://svn.boost.org/trac/boost/ticket/2335 When I tried to login, it wouldn't accept my userid or password. I remember using them not too long ago for: https://svn.boost.org/trac/boost/ticket/3044 Anyhow, tha attached code produces the following output: /home/evansl/download/gcc/4.4-20090519/install/bin/g++ -c -Wall -ftemplate-depth-100 -O0 -fno-inline -I/home/evansl/prog_dev/boost-svn/ro/boost-trunk -DTEMPLATE_DEPTH=100 -DINTEGRAL_CONSTANT_WORKAROUND_GCC_BUGZILLA_BUG_40092 vector_same.cpp -MMD -o /home/evansl/prog_dev/boost-svn/ro/boost-trunk/sandbox/build/gcc4_4n/boost-vrtmp/libs/fusion/sandbox/vector_same.o ... /home/evansl/download/gcc/4.4-20090519/install/bin/g++ /home/evansl/prog_dev/boost-svn/ro/boost-trunk/sandbox/build/gcc4_4n/boost-vrtmp/libs/fusion/sandbox/vector_same.o -o /home/evansl/prog_dev/boost-svn/ro/boost-trunk/sandbox/build/gcc4_4n/boost-vrtmp/libs/fusion/sandbox/vector_same.exe /home/evansl/prog_dev/boost-svn/ro/boost-trunk/sandbox/build/gcc4_4n/boost-vrtmp/libs/fusion/sandbox/vector_same.exe N5boost6fusion7vector2IffEE count*sizeof(float)=8 sizeof(float_container_type)=8 So, at least for my system: uname -a Linux evansl-desktop 2.6.24-24-generic #1 SMP Wed Apr 15 15:11:35 UTC 2009 x86_64 GNU/Linux there's no problem.
On 05/29/09 14:32, Larry Evans wrote: [snip]
I'll participate. However, I just tried to add a test case for my system to:
https://svn.boost.org/trac/boost/ticket/2335
When I tried to login, it wouldn't accept my userid or password. [snip] Sorry for noise. I should have read:
If you are just submitting bug reports, you probably don't need a Trac userid, from: https://svn.boost.org/trac/boost/
Does anyone care to look at the patch attached to #1791? It's a simple warning suppression, and it's been hanging around for a while. Thanks, Richard Webb -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
Richard Webb wrote:
Does anyone care to look at the patch attached to #1791? It's a simple warning suppression, and it's been hanging around for a while.
Thanks, Richard Webb
The most recent patch attached to #1507 would be nice as well :-) -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
AMDG Richard Webb wrote:
Richard Webb wrote:
Does anyone care to look at the patch attached to #1791? It's a simple warning suppression, and it's been hanging around for a while.
Thanks, Richard Webb
The most recent patch attached to #1507 would be nice as well :-)
I take it that the warnings in #1507 don't occur with msvc 7.1? In Christ, Steven Watanabe
Steven Watanabe-4 wrote:
I take it that the warnings in #1507 don't occur with msvc 7.1?
I'm not sure, and unfortunately i only have VC8+ around to test with at the moment. -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
Steven Watanabe:
AMDG
Richard Webb wrote:
Richard Webb wrote:
Does anyone care to look at the patch attached to #1791? It's a simple warning suppression, and it's been hanging around for a while.
Thanks, Richard Webb
The most recent patch attached to #1507 would be nice as well :-)
I take it that the warnings in #1507 don't occur with msvc 7.1?
I doubt it. These warnings aren't new.
Marshall Clow wrote:
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
Some procedural questions. I don't see a wiki page that describes the preferred ticket workflow. The TicketWorkflow page most discusses migration issues from SF. Should the ticket Type be changed to Patch if there is a patch and test case attached? Should tickets that are requiring some amount of work be "assigned" to the individual working on the ticket as an indicator to others that someone is already working the issue? Should the ML be used to request patch testing for additional platforms that patch creator does not have access to? Happy bug fix'n to all! michael -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com
----- Original Message ----- From: "Michael Caisse" <boost@objectmodelingdesigns.com> To: <boost@lists.boost.org> Sent: Saturday, May 30, 2009 6:47 PM Subject: Re: [boost] Second call: The Boost Bug Sprint is coming!!
Marshall Clow wrote:
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
Some procedural questions. I don't see a wiki page that describes the preferred ticket workflow. The TicketWorkflow page most discusses migration issues from SF.
Should the ticket Type be changed to Patch if there is a patch and test case attached?
I was asking myself the same question. This will help the maintainer to concentrate to the tickes possiblily having a solution, but the ML can be used also to request this to the maintainer. The problem is that we loss the information if it is a bug or a feature request. IMO the fact the ticket have a oatch and a test case that prove the issue is orthogonal, and should be stated using specific attributes. If any one knows how to add attributes to the TRAC system this will be very useful.
Should tickets that are requiring some amount of work be "assigned" to the individual working on the ticket as an indicator to others that someone is already working the issue?
This could help to organize this Bug Sprint, but once the patch and the test have been provided the ticket should be assigned to the maintainer, as he/she is the one that can decide to integrate or not the patch.
Should the ML be used to request patch testing for additional platforms that patch creator does not have access to?
I think so. I have already do that. Regards, Vicente
At 9:47 AM -0700 5/30/09, Michael Caisse wrote:
Marshall Clow wrote:
The boost bug sprint is coming! It starts _this_ Friday, May 28th, and runs through Sunday June 7th.
Some procedural questions. I don't see a wiki page that describes the preferred ticket workflow. The TicketWorkflow page most discusses migration issues from SF.
I wrote that page a while back. I'm open to suggestions on how to improve it ;-)
Should the ticket Type be changed to Patch if there is a patch and test case attached?
I'd rather not. I think that a feature request should be a FR, and a bug a bug, even if they have patches attached. My opinion is that we should get rid of the "patch" category entirely. -- -- Marshall Marshall Clow Idio Software <mailto:marshall@idio.com> It is by caffeine alone I set my mind in motion. It is by the beans of Java that thoughts acquire speed, the hands acquire shaking, the shaking becomes a warning. It is by caffeine alone I set my mind in motion.
Marshall Clow wrote:
At 9:47 AM -0700 5/30/09, Michael Caisse wrote:
Should the ticket Type be changed to Patch if there is a patch and test case attached?
I'd rather not. I think that a feature request should be a FR, and a bug a bug, even if they have patches attached.
My opinion is that we should get rid of the "patch" category entirely. Sounds good to me. This could be an appropriate use for keywords.
I have to admit, the type of patch doesn't make much sense. -- ---------------------------------- Michael Caisse Object Modeling Designs www.objectmodelingdesigns.com
Looks like the patch attached to #1599 was applied some time ago. -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
Richard Webb wrote:
Looks like the patch attached to #1599 was applied some time ago.
#2432 looks fixed as well. -- View this message in context: http://www.nabble.com/Second-call%3A-The-Boost-Bug-Sprint-is-coming%21%21-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.
participants (14)
-
Anthony Williams -
Beman Dawes -
Daniel Wallin -
Gennadiy Rozental -
Joel FALCOU -
Kevin Sopp -
Larry Evans -
Marshall Clow -
Michael Caisse -
Peter Dimov -
Richard Webb -
Steven Watanabe -
vicente.botet -
Vladimir Prus