Boost logo

Boost :

Subject: Re: [boost] [serialization] boost 1.45. I did not find any informationabout serios flaw in 1.44
From: Sergey Voropaev (serge-voropaev_at_[hidden])
Date: 2010-12-08 22:40:04


Robert Ramey <ramey <at> rrsd.com> writes:

>
> Sergey Voropaev wrote:
> > I am reporter of bug #4660
> > (https://svn.boost.org/trac/boost/ticket/4660). I am glad this bug
> > was fixed in 1.45 version. But I did not find any information in
> > release notes (http://www.boost.org/users/download/version_1_45_0)
> > and in library documentation
>(http://www.boost.org/doc/libs/1_45_0/libs/serialization/doc/index.html)
> > about what was fixed in 1.44 version. There are not any
> > recommendations or comments about using version 1.44 with binary
> > archives.
> > I think that the absence of such information is very dangerous for
> > the future of the serialization library, since this is a serious
> > indicator of the quality of maintenance of the library. (I have no
> > complaints about the quality of the library and its design)
> > Should I reopen this bug, or open a new one, or this letter would be
> > sufficient to restore order to the documentation of serialization
> > library?
> >
>
> I'll add some information to the documentation.
>
> Robert Ramey
>
There are some reports (https://svn.boost.org/trac/boost/ticket/4660)
about the lack of information and misunderstanding of the status
of this bug in version 1.45. So I decided to reopen this bug.

Sergey Voropaev

P.S
I think it is common problem for boost, but not only serialization
library. We have good quality and good design library (any library
from boost). This library is quite popular and many people use it.
But the author is now engaged in other projects and did not have
the time to support the library. It is very likely and expected
on a time scale of 10 years. But so many people around the
world use this code and depend on it...
I do not know the solution to this problem.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk