Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 21 Dec 2002 00:48:50 +1100
From:      Edwin Groothuis <edwin@mavetju.org>
To:        Maxim Sobolev <sobomax@FreeBSD.ORG>
Cc:        Akinori MUSHA <knu@iDaemons.org>, portmgr@FreeBSD.ORG, ports@FreeBSD.ORG
Subject:   Re: Thoughts about ports freeze
Message-ID:  <20021220134850.GY50581@k7.mavetju>
In-Reply-To: <20021220131339.GB11573@vega.vega.com>
References:  <20021220001529.GC9963@vega.vega.com> <86lm2ls3ei.wl@archon.local.idaemons.org> <20021220131339.GB11573@vega.vega.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 20, 2002 at 03:13:39PM +0200, Maxim Sobolev wrote:
> Well, all this is fine, but doesn't answer one of my main points: why
> do we shift responsibility for our inability to encourage fellow developers
> to pay attention to CURRENT not only to stable to our end users? And I
> doubt that such tactic will bring anything but users' dissatisfaction,
> because even a year-long freeze will not help to encourage reluctant
> developer, who doesn't have 5.0 and therefore doesn't care about it,
> to fix something. The only things that can push him into doing it
> are (a) if he will use 5.0 on day-to-day basis or (b) he will be
> flooded with problem reports from angry users running 5.0. The current
> freeze won't lead to neither (a), nor (b), instead it (from my own
> experience) leads to: (c) user makes a conclusion that FreeBSD
> release-engineering process sucks.

Chicken and egg problem.
Ports for 5.x don't get fixed until 5.0 gets out and comes into the
hands of a bigger group of people. For example, until a week ago I
didn't have access (well, not strictly true) access to a 5.0 machine.
And now I have it only because there is one in the FreeBSD serverfarm.

For me the ban can be lifted. I've gone through the list of problems
and done all I can. The ones I couldn't do are just too weird for
me (or I gave up after an hour looking at it). Please don't expect
me to fix problems in the code of others due to thighter rules that
the C compiler uses. If it isn't something obvious which can be
fixed in ten minutes, it's too complicated and the maintainer /
original author should have a look at it(*). Right now I'm going
1443 and rising (well, actually 790 if you only take the un-assigned
ones)

(*) Note that I don't mind spending time with the author about it.

Edwin

-- 
Edwin Groothuis      |            Personal website: http://www.mavetju.org
edwin@mavetju.org    |    Weblog: http://www.mavetju.org/weblog/weblog.php 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021220134850.GY50581>