release policy and quicklisp

Attila Lendvai attila at lendvai.name
Mon Feb 15 23:53:12 UTC 2016


the situation:

hu.dwim.sdl depends on the new cffi/c2ffi stuff, and it's needed for
projectured. to make playing with projectured simple, in its readme
and its build.sh we rely on ql.

ql takes its snapshot of CFFI from the CFFI release tgz, so
hu.dwim.sdl cannot be added to the next ql release.

my goals:

have a shorter "release" cycle when it comes to ql snapshots.

my proposal:

set up a branch called 'quicklisp' in the CFFI repo and change ql to
capture that instead of the release tgz. this is what VCS'es are
designed for after all.

sidenote:

i think in the long run it would be better to use a moving tag for
this, but for now the ql infrastructure doesn't support that for git
repos. unfortunately git doesn't handle well when history is
overwritten with a push -f on the remote side, but tags don't have
that problem (git fetch --tags readily overwrites local tags with the
remote ones).

a small glitch in this almost ideal release management scheme is that
git overwrites tags as opposed to keeping a stack of them and thus
doesn't presere their history.

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“You are what you do, not what you say you’ll do.”
	— Carl Jung (1875–1961)



More information about the cffi-devel mailing list