Re: [boost] mpl_core (Was: New dependency report)

Subject: Re: [boost] mpl_core (Was: New dependency report)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-06-09 03:37:03

On Sunday 08 June 2014 18:15:39 you wrote:
> On Sunday 08 June 2014 16:54:07 Peter Dimov wrote:
> 
> > Assuming that the tests are fine, I wonder what is the best way to proceed
> > from here.
> > 
> > Do people have objections to splitting these headers into a new submodule,
> > mpl_core?
> > 
> > My initial thought is that we can create the new submodule on a feature
> > branch in the superproject, so as to not affect develop and master at this
> > time. The feature branch will not automatically pick up any further
> > 'develop' changes in other modules, but that's probably not a problem.
> > (The
> > changes to the existing MPL module will need to also be done on a branch,
> > of course.)
> 
> I think we're safe to do this in develop. The extraction doesn't require
> code changes (yet, until we solve that TypeTraits dependency problem).
> However, I'd be fine if we do this in a separate branch and merge it after
> 1.56.

So what shall we decide?

FWIW, since there are no code changes, only file moves, it's safe to add the 
submodule to both develop and master. We can defer the code modifications 
until after release or make them in develop only or a separate branch, but 
this won't be possible if we don't create the submodule.