[boost] New but 'unsupported' libs Was: Status of the Boost.Property_tree library

From: Paul Baxter (pauljbaxter_at_[hidden])
Date: 2008-03-11 05:47:32

> 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?

I'd suggest the release manager consider leaving such libraries in the 
sandbox if they haven't got a commitment from an individual and they haven't 
yet been incorporated in a release. A first release is likely to shake down 
a library more than the review process and it is at this point the author or 
perhaps a maintainer is valuable. Indeed many libraries change radically 
enough after the review that they often benefit tremendously from the 
shakedown that first release gives them.

Perhaps new libs need a named sponsor as an entry criterion for 
incorporation?

I also appreciate that the current monolithic boost release cycle can be 
difficult for new library authors to make a commitment to in advance. Hence 
the sponsor may not necessarily be the author.

Once 'in', inevitably some maintainers will move on. I am grateful for their 
efforts and the library will then sink or swim on its merits. The issue of 
what to do or document for such libraries is not one I intended to cover in 
this email.