Re: [Boost-users] [serialization] class versioning changes in boost 1.42

Subject: Re: [Boost-users] [serialization] class versioning changes in boost 1.42
From: Peter Dimov (pdimov_at_[hidden])
Date: 2010-03-01 09:14:33

Jarl Lindrud wrote:
>> If, on the other hand, you use a single archive-level version
>> number, this creates a central point that every class change needs
>> to touch, and distributed development becomes a nightmare.
>
> I've actually implemented this, where I work. We have a large
> distributed application, where forward (and backward) compatibility
> are essential requirements.
>
> It's by no means automated, and there are some thorny issues when
> development proceeds on separate branches. Basically you only want to
> make schema changes on the trunk of your codebase. Assuming
> relatively few releases, you can collect a whole batch of changes
> into one version number change.
>
> I'm not sure what you mean by distributed development?

I mean independent component development by multiple uncoordinated teams. 
For example, if you use boost::X in the project, its serialization support 
can't follow your global versioning scheme. It works if you control all 
pieces.