Re: [Chicken-janitors] release management

[Ivan Raikov]

  I think it is a little more complicated than that. svn log does
not show any recent changes made to the release branch. I ran the
nightly snapshot script manually, and it was fetching the Chicken
source from the release branch instead of trunk. I have now changed
that, so the nightly snapshot works properly. And currently, it looks
like the release-tarball script always creates a new tarball for the
current release, which means that the checksum will keep
changing... So I will follow your advice and temporarily remove the
release-tarball script from the cron table, until I figure out a
better scheme for doing releases.

   -Ivan


Mario Domenech Goulart <address@hidden> writes:

>
> Apparently some changes were applied to the release branch.  The
> release branch should not be changed, unless there's a version change.
> Otherwise, the checksum will change and packagers will complain, even
> if the code isn't modified.
>
> We need to rethink the release process.  The approach being used
> nowadays is an adaptation from the time trunk was be the stable
> Chicken.  So, today we have a script which fetches and bootstrap
> Chicken from the release branch and publishes it at
> http://chicken.wiki.br/releases (the adaptation is that now this
> script uses release, not trunk).
>
> My suggestion is that we have a script which would be manually run
> when a new release is ready.  This script would generate the source
> tarball (with C file), windows and linux binaries, PDF manual and
> publish everything at http://chicken-wiki.br/releases (actually we
> have this script, but it is automatically run everyday.)