boost trac for upcoming libraries?
Hi, Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries? Thanks, Barend
On Mon, May 11, 2009 at 11:03 AM, Barend Gehrels <barend@geodan.nl> wrote:
Hi,
Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries?
Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries. What uses did you have in mind? --Beman
Beman Dawes wrote:
On Mon, May 11, 2009 at 11:03 AM, Barend Gehrels <barend@geodan.nl> wrote:
Hi,
Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries?
Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries.
I suspect confusion is very likely -- in particular, having bug report against proposed library with target milestone of 1.40 would be fairly confusing. Or, maybe there's some technical measure to limit possible values of properties for bug reports? - Volodya
Vladimir Prus wrote:
Beman Dawes wrote:
On Mon, May 11, 2009 at 11:03 AM, Barend Gehrels <barend@geodan.nl> wrote:
Hi,
Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries? Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries.
I suspect confusion is very likely -- in particular, having bug report against proposed library with target milestone of 1.40 would be fairly confusing. Or, maybe there's some technical measure to limit possible values of properties for bug reports?
How about just name the component clearly, i.e. "[prop] FooBar" and then remove the tag once accepted. (And choose a good prefix scheme that make the proposed libraries end up last in the list.) Cheers /Maarcus
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Marcus Lindblom Sent: 20 May 2009 08:58 To: boost@lists.boost.org Subject: Re: [boost] boost trac for upcoming libraries?
Vladimir Prus wrote:
Beman Dawes wrote:
On Mon, May 11, 2009 at 11:03 AM, Barend Gehrels <barend@geodan.nl> wrote:
Hi,
Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries? Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries.
I suspect confusion is very likely -- in particular, having bug report against proposed library with target milestone of 1.40 would be fairly confusing. Or, maybe there's some technical measure to limit possible values of properties for bug reports?
How about just name the component clearly, i.e. "[prop] FooBar" and then remove the tag once accepted. (And choose a good prefix scheme that make the proposed libraries end up last in the list.)
I think it would be *very* useful - but someone needs to work out the details. An extra target milestone might be 'Review'? Paul --- Paul A. Bristow Prizet Farmhouse Kendal, UK LA8 8AB +44 1539 561830, mobile +44 7714330204 pbristow@hetp.u-net.com
Is the Boost Trac system intended for official libraries only, or can we also use it for (to be) proposed libraries?
Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries.
I suspect confusion is very likely -- in particular, having bug report against proposed library with target milestone of 1.40 would be fairly confusing. Or, maybe there's some technical measure to limit possible values of properties for bug reports?
How about just name the component clearly, i.e. "[prop] FooBar" and then remove the tag once accepted. (And choose a good prefix scheme that make the proposed libraries end up last in the list.)
I think it would be *very* useful - but someone needs to work out the details.
An extra target milestone might be 'Review'?
Thanks for all answers. I think this will work and be useful for many libraries. However, our library (GGL) is quite large (also compared to other libraries), has several sub-components and, preparing for the review, will have an own library-specific roadmap and milestones (indeed one of them will be review). We will use those internally, and for the users we already have, for bugs, tasks and wishes. We now realize that it, at this moment, is not convenient to fit all these into the Boost trac. Regards, Barend
on Wed May 20 2009, Barend Gehrels <barend-AT-geodan.nl> wrote:
Is the Boost Trac system intended for official libraries only, or can we also
use it for (to be) proposed libraries?
Seems OK to me to use it for proposed libraries, as long as the use wouldn't cause confusion between proposed and accepted libraries.
I suspect confusion is very likely -- in particular, having bug report against proposed library with target milestone of 1.40 would be fairly confusing. Or, maybe there's some technical measure to limit possible values of properties for bug reports?
How about just name the component clearly, i.e. "[prop] FooBar" and then remove the tag once accepted. (And choose a good prefix scheme that make the proposed libraries end up last in the list.)
I think it would be *very* useful - but someone needs to work out the details.
An extra target milestone might be 'Review'?
Thanks for all answers. I think this will work and be useful for many libraries.
However, our library (GGL) is quite large (also compared to other libraries), has several sub-components and, preparing for the review, will have an own library-specific roadmap and milestones (indeed one of them will be review). We will use those internally, and for the users we already have, for bugs, tasks and wishes.
We now realize that it, at this moment, is not convenient to fit all these into the Boost trac.
Yeah, I've been wondering if launchpad.net might be a more appropriate bugtracking system for us, or for example if we can do better with a hybrid Trac system like OForge. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
participants (6)
-
Barend Gehrels -
Beman Dawes -
David Abrahams -
Marcus Lindblom -
Paul A. Bristow -
Vladimir Prus