Re: [Chicken-hackers] Egg plan for 5?

[Peter Bex]

On Fri, Dec 29, 2017 at 06:59:45PM -0800, Dan Leslie wrote:
> My apologies if this has been discussed and I've simply missed it when
> searching the archive, but I'm curious what plans are in place for
> upgrading eggs to Chicken 5?
> 
> I expect Chicken 5 is tossing backwards compatibility to the wind
> wherever it makes sense, being a major version release, and so I wonder
> what I must undertake as an Egg maintainer to prepare for the upgrade.

Hi Dan!

This is an excellent question.

There are some notes over at the wiki roadmap page about CHICKEN 5:
https://wiki.call-cc.org/chicken-5-roadmap#determine-how-to-make-chicken-4-eggs-live-alongside-chicken-5-eggs-incomplete

Basically, you can decide what you want to do.  CHICKEN itself does
not impose any restrictions about how to distribute eggs.

If you don't care about backwards compatibility for your eggs,
you can just add a new "my-egg.chicken-5.release-info" file to
your repo and ask us to add that to the egg locations.  Any new
releases will then be available only for CHICKEN 5.

You could simply create a new repo for the CHICKEN 5 version of the
egg, that way you can continue development on the old version too
without either getting in the way of the other.

Alternatively, you can move your master branch to "chicken-4" or so
and then ask us to change the release-info URL in the egg locations
to the one from that branch.  After that's been done, in master you
clear the release list, make it work with CHICKEN 5 and add new
release entries whenever you want to make a release.  Then we add
this egg to the CHICKEN 5 egg locations.

Finally, you could let master be for what it is and continue
development on a "chicken-5" branch.  This would be a bit awkward
after CHICKEN 5 has been out a while.

Cheers,
Peter

signature.asc
Description: PGP signature