chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] new release policy


From: Elf
Subject: Re: [Chicken-hackers] new release policy
Date: Sat, 1 Sep 2007 19:34:41 -0700 (PDT)


I tend to agree that no official releases is a Bad Thing, unless it's a
temporary change.

-elf

On Sat, 1 Sep 2007, Peter Bex wrote:

On Sat, Sep 01, 2007 at 07:28:37PM +0200, felix winkelmann wrote:
The chicken version has been bumped to 2.701, now. There will be
no more "official" releases from now on, just continuously created
snapshots.

IMHO this is not a good idea.  Other projects make official releases
with a reason.

An official release tells me that someone in charge considered the
code at that point in time as worthy of being distributed.  It means
it has been (hopefully) tested thoroughly, that no experimental new
features are in there that might mess things up and it provides one
with an easy way of tracking what issues people are having.

Not making releases makes Chicken even more of a moving target than
it already is.  It makes life unneccessarily difficult for packagers
and casual users.  It will possibly mean every single user could be
running a unique chicken version.  When someone reports a problem with
a stable version, people will be able to tell them "oh, that's a known
issue with version this-and-that", but if automatic snapshots are made
you can get the situation that there will be an intermittent problem
between two snapshots, and an unlucky person might just get the version
with this bug.

So I'm wondering: why do you want to make this change?

Cheers,
Peter





reply via email to

[Prev in Thread] Current Thread [Next in Thread]