[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] experimental branch
From: |
Felix |
Subject: |
Re: [Chicken-hackers] experimental branch |
Date: |
Sat, 25 Jun 2011 21:25:39 +0200 (CEST) |
From: Christian Kellermann <address@hidden>
Subject: Re: [Chicken-hackers] experimental branch
Date: Sat, 25 Jun 2011 18:39:24 +0200
>
> You are free to do whatever you want! :) I am not sure what your goal
> is there though. Salmonella atm can only test whatever is in git. So
> if you work hard on the latest and greatest stuff, we will know it
> breaks only after it hits the master branch. So maybe that also isn't
> that less stress you hope for?
I meant that I will develop directly on master. Only long-term work
(like "specialization") is intended to be on separate branches. So,
you will know soon enough when things break. :-)
>
> Also I am a bit confused about the branches that are currently on git.
> Which of these are considered "private" which are for the adventurous?
> So far I always liked (and run) the experimental branch.
Just use "master" if you are adventurous. The other branches are:
expander-simplifications Peter Bex' branch for expander fixes
specialization Optimizations based on an enhanced scrutinizer
(soon to be merged)
fat-symbols[-bootstrap] An experiment to implement "lazy" print-name
generation for gensyms (disappointing results,
and currently stale)
irregex-bugfixes Also by Peter Bex for irregex changes
prerelease Staging branch for development on releases
release Branch for the next release
spiffy-debug obsolete
The others I have deleted. No branch is "private", try whatevery you want.
> In any case http://wiki.call-cc.org/release-policy should reflect the
> current state of things or be deleted from the wiki.
True. I will update this page. Thanks for the reminder.
cheers,
felix