Return-Path: Delivered-To: apmail-incubator-river-dev-archive@minotaur.apache.org Received: (qmail 83129 invoked from network); 17 Jan 2011 22:11:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Jan 2011 22:11:43 -0000 Received: (qmail 4130 invoked by uid 500); 17 Jan 2011 22:11:43 -0000 Delivered-To: apmail-incubator-river-dev-archive@incubator.apache.org Received: (qmail 4085 invoked by uid 500); 17 Jan 2011 22:11:43 -0000 Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: river-dev@incubator.apache.org Delivered-To: mailing list river-dev@incubator.apache.org Received: (qmail 4077 invoked by uid 99); 17 Jan 2011 22:11:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 22:11:42 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [61.9.189.140] (HELO nschwmtas02p.mx.bigpond.com) (61.9.189.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jan 2011 22:11:33 +0000 Received: from nschwotgx01p.mx.bigpond.com ([61.9.223.241]) by nschwmtas02p.mx.bigpond.com with ESMTP id <20110117221109.LZJD25233.nschwmtas02p.mx.bigpond.com@nschwotgx01p.mx.bigpond.com> for ; Mon, 17 Jan 2011 22:11:09 +0000 Received: from [10.1.1.2] (really [61.9.223.241]) by nschwotgx01p.mx.bigpond.com with ESMTP id <20110117221109.DQJS8424.nschwotgx01p.mx.bigpond.com@[10.1.1.2]> for ; Mon, 17 Jan 2011 22:11:09 +0000 Message-ID: <4D34BD07.4020301@zeus.net.au> Date: Tue, 18 Jan 2011 08:04:55 +1000 From: Peter Firmstone User-Agent: Thunderbird 2.0.0.14 (X11/20080531) MIME-Version: 1.0 To: river-dev@incubator.apache.org Subject: [VOTE] Re: build mechanisms References: <4D2EDFE3.8000307@qcg.nl> <4D300E33.5080408@qcg.nl> <37E3C4E9-CABA-45B5-8FA4-BE5C088A6053@gmail.com> <4D305D78.2000609@qcg.nl> <4D32E028.3060400@zeus.net.au> <4D3408BF.2040201@qcg.nl> In-Reply-To: <4D3408BF.2040201@qcg.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150205.4D34BE7D.00AA,ss=1,fgs=0 X-Virus-Checked: Checked by ClamAV on apache.org Sim IJskes - QCG wrote: > On 16-01-11 13:10, Peter Firmstone wrote: >> demonstrate. When the time comes we'll all have an opportunity to >> analyse and discuss whether the modular build structure should be >> adopted, if the community decides not to adopt it for whatever reason, I >> will still have had the opportunity to learn much about River's >> structure. > > OK, i will hold all contributions until you have reported, and this > issue is settled. > Have you had a look at what Dennis contributed on River-300? Did you attempt to build it? Dennis supplied two alternate Modular system build examples. It took about 2 minutes to build a module on my machine, if the tests specific to the module are included, the build test cycle for a module is going to be very short, quite suitable for test driven development. At the moment, I'm putting this contribution into skunk so people without commit access can cooperate and submit patches against it. At this point in time I'm still investigating it myself, however I also have to recognise that my time is limited due to other work commitments and the time required to complete a modular build quite large. Until it is complete, we don't know for sure how well suited it is to building and testing River. What I can say from my investigations to date is that it looks very promising. But on the other hand this work seems to be dividing the development community, so I have to weigh up the benefits of pursuing it further. If I continue to pursue the modular build investigation, it creates uncertainty for developers whom have planned improvements for the current build process. Since the build process plays a key role in development, continuing to investigate the modular build process, without making a decision, risks stagnating the project, due to uncertainty. Sometimes no decision is the worst decision. So based on the knowledge we have so far, I'm asking you all to cast a vote on whether you want a modular build or or keep the existing build. I hope that whatever the vote result may be, we are all able to move forward and continue working productively together. Regards, Peter.