Re: [boost] New but 'unsupported' libs Was: Status of theBoost.Property_tree library

From: Darryl Green (Darryl.Green_at_[hidden])
Date: 2008-03-11 20:25:15

> -----Original Message-----
> From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]]
> On Behalf Of Paul Baxter
> 
> > What is the status of the Boost.Property_tree library?  I notice it
is
> now
> > in the SVN trunk.   Does this mean it will be part of the next
release?
> >
> > <https://svn.boost.org/svn/boost/trunk/boost/property_tree/>
> 
> I really like the simplicity of this library but this is about the
third
> or
> fourth request in the last few months without a reply.
> 
> This is not a slight on the original author or this library, but it
does
> bring up the more general question..
> 
> Does boost really want to put an 'unsupported' new library into a
release?
> 

Yes - if it has adequate tests and they pass? If the library is failing
tests or has a significant number of bug reports that have not been
addressed it should not be included in the release. Given the current
branching scheme as I understand it this should not be a significant
problem and should not require the library to be "relegated" to the
sandbox.

There are obviously a range of possible risks here - a library
containing a lot of template metaprogrammming and associated compiler
dependent quirks/workarounds is, in general, more likely to:

1) Have latent bugs dependent on usage (as well as compiler)
2) Exhibit new/changed behaviour with new compiler releases

The former of these should result in bug reports. The second should be
found in automated testing.

In any case, I don't believe Property_tree falls into this category and
would seem to be a library that "anyone" could step up to the plate and
elect to maintain. I would also hope that it would be a library that
could be maintained relatively easily with the assistance of the broader
boost community - ie. user submitted patches. With trac etc. in place
this process should be more effective than it has been in the past.

I should note in the particular case of Property_tree, I am a
(new/recent) user. It works for me, if it didn't you would have a trac
bug submission (with test and patch)... Of course with no maintainer,
that might not be much help.

##########################################################################
CONFIDENTIALITY NOTE: Please consider our environment before printing this
email.This email and any attachments are confidential and may be subject to
copyright, legal or some other professional privilege. They are intended
solely for the attention and use of the named addressee(s). They may only
be copied, distributed or disclosed with the consent of the copyright owner.
If you have received this email by mistake or by breach of the 
confidentiality clause, please notify the sender immediately by return
email and delete or destroy all copies of the email. Any confidentiality,
privilege or copyright is not waived or lost because this email has been
sent to you by mistake. 

##########################################################################