From owner-freebsd-ports@FreeBSD.ORG Sat Jan 25 12:35:41 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02C6A6CC for ; Sat, 25 Jan 2014 12:35:41 +0000 (UTC) Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AF5D81DEA for ; Sat, 25 Jan 2014 12:35:40 +0000 (UTC) Received: by mail-qa0-f41.google.com with SMTP id w8so5264120qac.0 for ; Sat, 25 Jan 2014 04:35:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Y+zp3j9S4yV9Mf7zTfxc1bi6GH0S2AVm57jfI3iGwhc=; b=lPFXoiMlq+XqGGIc9nqMFZ2jy4wyyDhj8GAcB0vJrMksScc2Bhg3d6+UefsB8mUSuh 6NpHk+sA3uF/B8EohYSDlA8aP3KVe8Krcw6oEIGRP/iHXH3w+gPilcmy0ti7E2LrkfWC ZAaFebYXs5wzut07oHKP7edNJ91I/dHegYvzFyqhv8vfuBx3ob0oY4EimN3uXqXh7mq2 Gvg59LkuupwPJKfpiGBTDQxVB3CBrO1Cw8ykwylSd+0kfz9NaN5RAMyGRIh3/HCe5x2X dlF64kBEE61wpUAdHh6udWAcJWNLZq7oqSj2/EH5wlwj/UCtN5WXuo1Yd5N533+0Lkaq eXZA== MIME-Version: 1.0 X-Received: by 10.224.14.70 with SMTP id f6mr28220084qaa.31.1390653339883; Sat, 25 Jan 2014 04:35:39 -0800 (PST) Received: by 10.229.208.202 with HTTP; Sat, 25 Jan 2014 04:35:39 -0800 (PST) In-Reply-To: References: Date: Sat, 25 Jan 2014 13:35:39 +0100 Message-ID: Subject: Re: What is the problem with ports PR reaction delays? From: Big Lebowski To: =?UTF-8?Q?Bernhard_Fr=C3=B6hlich?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Aryeh Friedman , ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jan 2014 12:35:41 -0000 On Sat, Jan 25, 2014 at 1:13 PM, Bernhard Fr=C3=B6hlich = wrote: > > Am 25.01.2014 02:12 schrieb "Aryeh Friedman" : > > > > > > > > > I think you've got me wrong - I am following freebsd-virtualization > list > > > very closely, and the matter I've touched here is not my doubt on whi= ch > > > technology I should use, but rather a complaint on the state of jails > > > related tools directly leading to the delays in handling of ports > related > > > PR's. I know the technology alternatives, I am decided to jails for a > > > reason, and I also know your work on the web interface focusing on > bhyve, > > > but its not about it. > > > > > > > My point is writing scripts for VM's is easier (nothing more then copy > the > > master and then do a normal make install/portmaster on the port of you > > choice [better to run them one at a time I have found). When I get int= o > > port testing I usually have 3 VM's on the host working on compiling and= 1 > > for development. I have yet to find a good way to have 4 jails runnin= g > as > > independentlu. > > This thread has taken a different direction at some point so I want to > throw in another view. > > We already have all that build testing stuff around for various FreeBSD > versions with enough hardware resources and production ready and free for > all. It's called redports.org and I have even already created scripts > that monitor the gnats database for ports PRs with patches, fetch them, > apply them to the redports repository and schedule jobs for it. > > So it is all there and the reason why it isn't running already are > political ones because I also proposed to automatically send followup mai= ls > to the PR with the buildlog status. > > http://code.google.com/p/redports/source/browse/#svn%2Ftrunk%2Fscripts > That sounds great! It would be awesome to introduce both solutions (automated testing and screening roles with new volunteers - we already have two of those) to improve the process. However, I hate when I hear 'politics' in open source projects. Could you be more specific and name the problem, if you mentioned it? B.