[Scons-dev] Progress blockers

[Gary Oberbrunner]

On Mon, Feb 4, 2013 at 12:43 AM, William Deegan
<bill at baddogconsulting.com>wrote:


> Russel,

>

>

> On Feb 3, 2013, at 9:31 PM, Russel Winder <russel at winder.org.uk> wrote:

>

> > The current SCons workflow assumes that each developer has access to all

> > platforms for testing prior to creating a pull request and/or

> > committing. We need to set up a CI service that can be used to test any

> > submitted request on all major platforms.

> >

> > So, I am working on D support but in a fork because there are breakages

> > on certain platforms that I have no access to. Catch-22: the stuff

> > cannot get merged in to the mainline because it cannot be tested and it

> > cannot be tested because it cannot be merged in to the mainline. Without

> > a multi-platform team effort this means nothing can ever get merged into

> > the mainline. Thus progress is halted. Hence lack of enthusiasm for

> > doing any work on SCons core.

> >

> > There must be some SCons user organizations out there who can contribute

> > back to SCons development by offering CI build resources?

>

> We already have:

> buildbot.scons.org

>

> Likely what we'd need to assist you is to have D installed on win32?

>


Sounds like it.  I think Russel's also asking for a way to build branches
with the buildbot; that way he and/or others could commit some D code on a
branch, submit to the buildbot (somehow), and iterate until all platforms
work.  Russel, is that an accurate summary?

-- 
Gary
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://two.pairlist.net/pipermail/scons-dev/attachments/20130204/77d2ffbd/attachment.htm>