Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <009c01c2c63f$b1080f90$78d96f83@pomello>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>, "William A. Hoffman" <billlist AT nycap DOT rr DOT com>
References: <5 DOT 2 DOT 0 DOT 9 DOT 0 DOT 20030127132032 DOT 031f91e0 AT pop DOT nycap DOT rr DOT com>
Subject: Re: Cygwin Release process
Date: Mon, 27 Jan 2003 20:07:16 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

William A. Hoffman wrote:
> So, from the feedback I am getting, it really boils down to a "not
> enough people to maintain the feature" issue.  I don't think that
> people don't think that a stable release of cygwin would be a bad
> thing, it is just that there
> is no one to maintain it.
>
> The least intrusive approach I can think of is the following:
>
> Once a quarter, there is a cygwin release.   All packages in curr, get
> automatically moved to cygwin-cur once a quarter.
>
> cygwin-curr, prev, curr, exp
>
> If bugs are reported for packages in cygwin-curr, they can be fixed,
> but no new versions are allowed.   I would expect that this would
> provide a more stable cygwin with not much manual effort.
>
> I guess the problem is to convince folks, that this is a useful thing
> to do. As a cygwin user, I think it would provide a more stable
> platform.

I think it would unnecessarily delay people from updating to latest package
versions.
The point is *[curr] is meant to be stable*. Occasionally a problem may slip
through. Fine. That's what the option of reverting a package to [prev] is
for. When problems arise, they are fixed quickly, or the package is pulled,
and the [prev] reinstated to [curr].

If this is not good enough for you, then *just burn a CD*. There is no need
to force this artificial 'release' policy on the Cygwin project.


Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/