Date: Sat, 12 Jan 2008 10:16:29 +0000 From: "Igor Mozolevsky" <igor@hybrid-lab.co.uk> To: ticso@cicely.de Cc: Mark Linimon <linimon@lonesome.com>, freebsd-current@freebsd.org, Peter Schuller <peter.schuller@infidyne.com> Subject: Re: Improving the handling of PR:s Message-ID: <a2b6592c0801120216i1f1b4887n2f3653303f1112a2@mail.gmail.com> In-Reply-To: <20080112002305.GE79270@cicely12.cicely.de> References: <478556AD.6090400@bsdforen.de> <20080110003524.GB5188@soaustin.net> <200801111935.50821.peter.schuller@infidyne.com> <20080111211019.GC79270@cicely12.cicely.de> <a2b6592c0801111520n173b4240p41d105c936f425ee@mail.gmail.com> <20080112002305.GE79270@cicely12.cicely.de>
index | next in thread | previous in thread | raw e-mail
On 12/01/2008, Bernd Walter <ticso@cicely12.cicely.de> wrote: > > Drawback: more work for the committers. > > Advantages: people feel rewarded for contributing patches, more > > hardware support... > > Yes and others with fine running hardware feel unsure about it. > The result are new reports or just other users that run away. > It is up to the commiter to get the balance of things that likely > don't break other HW and those that are risky and need further > verification. > If it is considered to risky the commiter has to find others to test. > See the list for patches, which are published for public testing. > This happens for exactly the purpose that the commiter thinks it has > some risky nature. I thought that was the whole point of CURRENT/BETA/RC? You can either hope that the committer will eventually find someone with same/similar hardware and that they're willing to experiment with it (although, why would anyone try running something that is considered risky on a production system is beyond me), *or* you can force everyone ot test it (given they have the right hardware) and push it into CURRENT or the next BETA where people expect to have glitches in... Igorhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a2b6592c0801120216i1f1b4887n2f3653303f1112a2>