Each month I take a snapshot of SLIME from CVS and include it in Quicklisp. When development was slow, this rarely resulted in broken versions. Now that development has moved to git and picked up speed, I'm concerned about including a version of SLIME that might have some temporary brokenness.
Can you recommend a way to raise the odds that Quicklisp uses a very good version of SLIME?
Zach