[serialization] patching 1.43 for the version numbering issue
Hi Robert, As we were discussing the other day, I'd like to just patch my 1.43 release to fix the serialization library versioning issue so that my archives created with it won't need to have the utility run on them for 1.44+ to understand them. I just want to verify with you that changing the version number in serialization/src/basic_archive.cpp is all that's needed. In your recent trunk change you increased the version for 1.44 to '8': https://svn.boost.org/trac/boost/changeset/64157 However, the 1.43 source seems to have version '7' already. I must be missing something as I don't see how binary archived were using library version '6' for 1.42/43. Thanks, -Ryan
Ryan Gallagher wrote:
Hi Robert,
As we were discussing the other day, I'd like to just patch my 1.43 release to fix the serialization library versioning issue so that my archives created with it won't need to have the utility run on them for 1.44+ to understand them. I just want to verify with you that changing the version number in serialization/src/basic_archive.cpp is all that's needed.
In your recent trunk change you increased the version for 1.44 to '8':
https://svn.boost.org/trac/boost/changeset/64157
However, the 1.43 source seems to have version '7' already. I must be missing something as I don't see how binary archived were using library version '6' for 1.42/43.
My understanding is that the last version # used before 1.44 is 6 and the only way the 7 should be found there is if fix_six is executed on that archive. To summarize: 1.41 version 5 1.42 version 6 1.43 version 6 - change to 7 with fix_six 1.44 version 8 Robert Ramey
Thanks,
-Ryan
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Robert Ramey <ramey <at> rrsd.com> writes:
My understanding is that the last version # used before 1.44 is 6 and the only way the 7 should be found there is if fix_six is executed on that archive.
To summarize: 1.41 version 5 1.42 version 6 1.43 version 6 - change to 7 with fix_six 1.44 version 8
That was my understanding too. However, I just downloaded 1.43 and libs/serialization/src/basic_archive.cpp has the following: // 5 - Boost 1.36 // changed serialization of collections: adding version even for primitive // types caused backwards compatibility breaking change in 1.35 // 6 - Boost 1.41, serializing collection sizes as std::size_t BOOST_ARCHIVE_DECL(version_type) BOOST_ARCHIVE_VERSION(){ return version_type(7); } Perhaps 1.43 was already correct? Or was the versioning done some other way? -Ryan
Ryan Gallagher wrote:
Robert Ramey <ramey <at> rrsd.com> writes:
My understanding is that the last version # used before 1.44 is 6 and the only way the 7 should be found there is if fix_six is executed on that archive.
To summarize: 1.41 version 5 1.42 version 6 1.43 version 6 - change to 7 with fix_six 1.44 version 8
That was my understanding too. However, I just downloaded 1.43 and libs/serialization/src/basic_archive.cpp has the following:
// 5 - Boost 1.36 // changed serialization of collections: adding version even for primitive // types caused backwards compatibility breaking change in 1.35 // 6 - Boost 1.41, serializing collection sizes as std::size_t
BOOST_ARCHIVE_DECL(version_type) BOOST_ARCHIVE_VERSION(){ return version_type(7); }
Perhaps 1.43 was already correct? Or was the versioning done some other way?
hmmm if that's the case the fix_six shouldn't be necessary. I got my information from looking at the SVN. But I might have gotten it wrong as it's sort of confusing to follow things as they migrate from trunk to release and then coordinate that with the actual release dates. Robert Ramey
Perhaps 1.43 was already correct? Or was the versioning done some other way?
I can confirm that the official 1.43 uses version number 7. <boost_serialization signature="serialization::archive" version="7"> Best Regards, Christoph
Robert Ramey <ramey <at> rrsd.com> writes:
hmmm if that's the case the fix_six shouldn't be necessary.
I just downloaded the 1.42 release and it also has version '7'.
I got my information from looking at the SVN. But I might have gotten it wrong as it's sort of confusing to follow things as they migrate from trunk to release and then coordinate that with the actual release dates.
Yeah, I tried that originally too. What I don't understand is why there are not clear tags svn for the releases. I haven't used svn itself much, but I figured that this would be part of the release process. -Ryan
On 28 July 2010 18:02, Ryan Gallagher <ryan.gallagher@gmail.com> wrote:
Yeah, I tried that originally too. What I don't understand is why there are not clear tags svn for the releases. I haven't used svn itself much, but I figured that this would be part of the release process.
There are: http://svn.boost.org/svn/boost/tags/release/ Daniel
Daniel James <dnljms <at> gmail.com> writes:
There are:
D'oh, thanks, I was looking for them a level up and missed "release" -Ryan
participants (4)
-
Christoph Heindl -
Daniel James -
Robert Ramey -
Ryan Gallagher