Boost logo

Boost-MPI :

Subject: Re: [Boost-mpi] [EXTERNAL] master vs develop
From: Alain Miniussi (alain.miniussi_at_[hidden])
Date: 2014-11-19 02:57:01

Hi Noel,

Thank for the infos.
No, I am not familiar with the boost testing pages, could you point me
to some informations ?
I was only able to find a mailing list

I guess I can contribute for those two libraries, at least on our
supported platform (linux/intel).



On 19/11/2014 06:11, Belcourt, Kenneth wrote:
> Hi Alain,
> On Nov 18, 2014, at 3:48 AM, Alain Miniussi <> wrote:
>> I have a question regarding:
>> I guess that all the commit, specially the pull requests, listed are those that made their way to develop but not to master.
>> What is the protocol/usage for having the stuff on the develop branch merge onto the master branch ?
> Generally I’ve been waiting for testing to cycle for a while before merging changes to master.
>> I guess the stuff on develop is already considered as being validated in some way, so what is needed for the next step ? does some testing report need to be produced ? on a specific set of platform ?
> Since very few people test Boost MPI on develop or master, I try to be very cautious with commits to develop and merges to master. It’s kinda easy to break things and, given the scarcity of MPI and Graph Parallel testers, I prefer to test the PR’s, develop and master branches on internal resources to ensure I don’t hit any problems before I push them to github.
> Are you familiar with the Boost testing pages? Can you contribute any testing resouces to specifically test MPI and Graph Parallel?
>> Also, does everything that is in master supposed to go automagically in the next release ?
> Generally yes, everything in master goes into the release, that’s why we’re careful about what ends up in master.
> — Noel
> _______________________________________________
> Boost-mpi mailing list
> Boost-mpi_at_[hidden]


Boost-Commit list run by troyer at