Re: [Chicken-users] Re: Chicken release policy

[Ivan Raikov]

Hello,

   I have disabled the script that used to rebuild the release
tarballs every night, so now the release tarballs should never, ever
get clobbered. The development snapshot script only builds from trunk,
so if the version number is increased in the prerelease branch, this
would not result in a new development snapshot. I plan on manually
enforcing version numbers to minimize the possibility of the 3.0.101
situation you describe. Of course, the success of this policy relies
on the cooperation of developers -- if people just start increasing
the version number at will, this might lead to out-of-order
versions. So we'll see how this goes.


   -Ivan


Aleksej Saushev <address@hidden> writes:

>
> 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.
>
> 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.
>
> Anyway, it is big progress, that you managed this. My congratulations!
> It makes it much easier to package it for distribution along with common
> systems.