Re: [boost] [Review] Phoenix review starts today, September 21st

Subject: Re: [boost] [Review] Phoenix review starts today, September 21st
From: Paul A Bristow (pbristow_at_[hidden])
Date: 2008-09-29 09:14:22

>-----Original Message-----
>From: boost-bounces_at_[hidden] 
>[mailto:boost-bounces_at_[hidden]] On Behalf Of David Abrahams
>Sent: 29 September 2008 12:59
>To: boost_at_[hidden]
>Subject: Re: [boost] [Review] Phoenix review starts today, 
>September 21st

>> Again, let me reiterate, that despite all these changes, the design
>> and implementation or V2 is still sound, and IMO, pretty much up
>> to standards with Boost quality. It is still the solid basis for
>> V3 with up to 95% of the interface intact and essentially unchanged
>> design and structure.
>
>In case *I* wasn't sufficiently clear about it, let me try to be
>painfully explicit: we may want to discuss whether it's good for Boost
>or its users if we release a new top-level library and then break its
>interface in the next release, three months later.  I'm all for
>accepting some version of Phoenix, but I want to make sure that users'
>needs for -- and the public perception of -- Boost's stability are
>accounted for.

I don't see that providing V3 *as well as V2* is breaking anything.

Surely it is quite clear that V2 and V3 are different beasts, and if you want to jump from one to the other, you risk some trouble.

This is price of improvement : I think Joel's proposed way of managing it is fine.

Paul

---
Paul A Bristow
Prizet Farmhouse, Kendal, Cumbria UK LA8 8AB
[phone] & SMS, Mobile [phone] & SMS
pbristow_at_[hidden]