Re: [boost] RFC: Separating Boost.Python from Boost

Subject: Re: [boost] RFC: Separating Boost.Python from Boost
From: Rob Stewart (rob.stewart_at_[hidden])
Date: 2015-05-29 18:03:00

On May 29, 2015 5:25:14 PM EDT, Stefan Seefeld <stefan_at_[hidden]> wrote:
> On 29/05/15 03:35 PM, Nevin Liber wrote:
> > I am strongly against breaking up the Boost release.
> 
> Just for context: We recently had a discussion (with Niall) where the
> idea of a "Boost distribution" came up. In such a scenario, Boost
> libraries could still follow their individual release schedule, but
> would be made available through a single distribution channel (which
> could also assume some validation tasks to test inter-version
> compatibility. I think this would be an interesting model to consider,
> as it adds the best of both worlds: independence an autonomy of
> projects, and convenience for end users.

That single distribution channel is the monolithic Boost release. There are no plans to replace that anytime soon.

> > I also think such a fundamental change has to go through the
> > Steering Committee.
> 
> Well, I beg to differ. It's the projects' maintainers / developers who
> have to do the actual work, so ultimately it's their decision where to
> put their effort.

If your changes have the effect of removing Boost.Python from Boost releases, then they have broader implications than the convenience or wishes of the maintainers.

___
Rob

(Sent from my portable computation engine)