On Mon, Dec 17, 2012 at 11:36 AM, Dave Abrahams <dave@boostpro.com> wrote:
on Sun Dec 16 2012, "Peter Dimov" <lists-AT-pdimov.com> wrote:
On Sat, Dec 15, 2012 at 9:42 PM, Dave Abrahams <dave@boostpro.com> wrote:
I'm sorry, but I have always intended to do what Julian thought:
Beman Dawes wrote: produce
an initial "develop" branch corresponding to "trunk" along with "master."
No problem. Daniel P has committed to updating the conversion script so that will happen, and I've just now updated docs accordingly.
I wonder how testing will work. Will the "develop" and "master" branches of each repo be tested?
What's going to be tested is fluid. The ultimate goal is to allow developers to request specific combinations of tests with each commit by modifying a .json file in their project's root directory. In the meantime, I expect to test every commit on any branch.
The biggest question is against which versions of Boost dependencies the commit will be tested. The obvious choices are 1. the version that was part of the last boost release, and 2. the last version of the dependency to be individually released (i.e. that dependency's "master" branch).
Feedback/opinions on that choice are most welcome.
Since there are clearly some decisions outside of my understanding as testing manager, and part of the release team... Could someone please comment on what is expected for the release that is based from github? Because barring any other direction testing will be exactly what it is right now.. Which is to test the the *release* (either trunk/develop of release/master branches) structure of Boost. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo