Re: [Boost-testing] Request for new 'unresolved issues' view

From: David Abrahams (dave_at_[hidden])
Date: 2005-06-15 16:53:01

Markus Schöpflin <markus.schoepflin_at_[hidden]> writes:

> David Abrahams wrote:
>
>> Markus Schöpflin <markus.schoepflin_at_[hidden]> writes:
>
>>>David Abrahams wrote:
>
>>>>What would a platform maintainer do?  Post patches?
>
>>>Basically what I'm currently doing for Tru64. Run the regression tests if 
>>>possible, and try to fix platform specific failures, either by posting 
>>>patches (for bigger changes), or by silently committing small fixes, or by 
>>>nudging the library author to have a look at it. And ideally pester the 
>>>compiler vendor with bug reports.
>
>>>>If you have a vision for how this would work, I encourage you to
>> 
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>>>>start a platform maintainers' program.  You could be, maybe, the
>>>>"maintenance wizard."
>
>>>What do you have in mind with such a program? And what would be a 
>>>maintenace wizard's job? Keep track of the platform maintainers?
>
>> I'm not the one with the vision, here ;-)
>
> I wouldn't choose such a grand word for it. :-) And I don't think we need a 
> "program" or a "wizard". Just a simple list with people who are doing what 
> I outlined above for certain platforms will do nicely, I think.

Everything has to be administered, at least a little.  Someone needs
to maintain the list, at the very least, and I can imagine all kinds
of things that *could* come up requiring someone to make an executive
decision.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com