[Chicken-users] Re: Chicken release policy

[Aleksej Saushev]

Mario Domenech Goulart <address@hidden> writes:

> Hi Aleksej,
>
> On Wed, 12 Mar 2008 20:38:53 +0300 Aleksej Saushev <address@hidden> wrote:
>
>> Ivan Raikov <address@hidden> writes:
>> 
>> >    I have created a draft wiki page that outlines the release policy
>> > for Chicken. It is available from the following URL:
>> >
>> >       http://chicken.wiki.br/release-policy
>> 
>> It would be nice, if it prevented creating of tarballs with the same name.
>> From the published page it isn't clear, if the released chicken-3.1.0.tar.gz
>> is the unique package with the name "chicken-3.1.0.tar.gz" and no development
>> snapshot gets the same name.
>
> Maybe they can have the same name, but they'd be stored in different
> directories (and available from different URLs).

You still don't get it.  The whole point is to have distributed files _properly_
labelled, the existance of two distributed bundles with the same name
"chicken-x.y.z.tar.gz" should be avoided. User should be free from dealing
with policies manually, it is up to policy to make him free and safe to choose
the same download directory for releases, either stable or unstable ones.

Because that is the natural way, user expects this behaviour, and it isn't
a good way to enforce user reading release policy, if the only thing he wants
is to check, whether some bug is fixed in later development snapshot.

>> There's a time window between creating 3.1.0 and bumping trunk from 3.0.99
>> to 3.1.1, is it possible that 3.1.0, which is frozen 3.0.99, be less fresh
>> than 3.0.101? It shouldn't be, if you want linear order on versions.
>
> Yeah, I think that should be avoided.

When you distribute two "chicken-3.1.0.tar.gz" files, it isn't clear,
which one is later, development snapshot (isn't it pre-release?) or released.
I don't know, what user expects in this case, so this must be confusing,
if your future clarification is consistent with expectations, and in your scheme
this isn't clear as well.

This is another argument to have development snapshots to start with 3.1.1.


-- 
CKOPO BECHA...
   CKOPO CE3OH...