Re: [Chicken-hackers] new release policy

[Ivan Raikov]

  I also think that it is good to have stable milestone releases every
once in a while. It greatly simplifies binary package management and
maintenance. Is there any way to convince you to bring back
milestones? I am willing to put in whatever effort it takes to make
stable releases, if you don't want to deal with that. 

  -Ivan

Peter Bex <address@hidden> writes:

> 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.