Subject: Re: [Boost-mpi] [EXTERNAL] master vs develop
From: Alain Miniussi (alain.miniussi_at_[hidden])
Date: 2014-11-19 11:15:52
So the results are coming, you can look for the files starting with
I'm running for master and develop. I'm running all the tests this time
but will probably limit them to mpi and graph-parallel (linux-intel is
probably well tested for non mpi stuff I guess).
As a side note: What about pull requests limited to documentation ? I
guess these are not tested by run.py right ?
On 19/11/2014 06:11, Belcourt, Kenneth wrote:
> Hi Alain,
> On Nov 18, 2014, at 3:48 AM, Alain Miniussi <alain.miniussi_at_oca.eu> 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 Ive 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. Its kinda easy to break things and, given the scarcity of MPI and Graph Parallel testers, I prefer to test the PRs, develop and master branches on internal resources to ensure I dont 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, thats why were careful about what ends up in master.
> Boost-mpi mailing list
-- --- Alain
Boost-Commit list run by troyer at boostpro.com