Date: Sat, 25 Jan 2014 14:43:12 +0100 From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= <decke@bluelife.at> To: Big Lebowski <spankthespam@gmail.com> Cc: Aryeh Friedman <aryeh.friedman@gmail.com>, ports <freebsd-ports@freebsd.org> Subject: Re: What is the problem with ports PR reaction delays? Message-ID: <CAE-m3X2rWk-0k_yH1PK0iN_5YhvSh1UsV0VCrroJq==687X1ZQ@mail.gmail.com> In-Reply-To: <CAHcXP%2BdtHPHT%2BFD8RdcqhGANBPf1Gk4N4coEpZY-eAuQE3iZtg@mail.gmail.com> References: <CAHcXP%2Bf6e-t--XbQPTH1goJp_CL7P=zTj5trZVWd4YZ_EsO9gw@mail.gmail.com> <CAGBxaX=t3e5SXoBDHnzAbx=SWbEFMJHNPQL13FnwNgKWM3gCiA@mail.gmail.com> <CAHcXP%2Bew5qt5hc9Y%2BR_njPkfhUMsDDAqNk9aYSacV4PwBmqjfw@mail.gmail.com> <CAGBxaXnXwo4JxnRdffZfdvfETfhgJNkFM-N23H1SOT0G3-oMwA@mail.gmail.com> <CAE-m3X2dQTTsbrTJg2iPT3qkfq7h9U8oGbRZXGAXH%2BJ2T4MFNw@mail.gmail.com> <CAHcXP%2BdtHPHT%2BFD8RdcqhGANBPf1Gk4N4coEpZY-eAuQE3iZtg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 25.01.2014 13:35 schrieb "Big Lebowski" <spankthespam@gmail.com>: > > > > > On Sat, Jan 25, 2014 at 1:13 PM, Bernhard Fr=F6hlich <decke@bluelife.at> wrote: >> >> >> Am 25.01.2014 02:12 schrieb "Aryeh Friedman" <aryeh.friedman@gmail.com>: >> >> >> > >> > > >> > > 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 which >> > > technology I should use, but rather a complaint on the state of jail= s >> > > 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 into >> > 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 running 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 mails 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. With the scripts it should be possible to fetch the patch of a PR, apply and commit it to your redports repository and do additional changes until you are okay with it. What is still missing is a script that helps committing the changes to the FreeBSD tree but it's really not that complicated to write that. > However, I hate when I hear 'politics' in open source projects. Could you be more specific and name the problem, if you mentioned it? The raised concerns were that automatic build testing might result in less testing on committer side. I agree that this might happen and automatic build testing is only one part of what committers need to do. A huge backlog and no response for months is definitely nothing we want.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAE-m3X2rWk-0k_yH1PK0iN_5YhvSh1UsV0VCrroJq==687X1ZQ>