SBCL Internals The pages on this CLiki-driven site can be edited by anybody at any time. No warranty of any kind can therefore be made; any implied warranties of merchantability or fitness for a particular purpose are expressly disclaimed

How to commit properly

As a general rule, you should bump the revision number in "version.lisp-expr" when committing. Also prefix your commit message with the bumped version number. This helps with generated changelogs. Also, given CVS's design, it is a good way of keeping track of related changes.

Think of a useful log message. Give an overview of what you have changed. When people want to know the details, they can run "cvs diff", of course.

Behaviour during Release freeze time

We release approximately once a month, around the 25th or so. Before the release happens, there is a feature freeze period. Some sample rules for this time of month:

• Compile on platforms that don't see much use (Alpha, SGI, whatever)
• Compile user code (clx, mcclim, paserve, araneida, etc)
• Compile test suites (clocc-ansi-test, pfdietz' suite, cl-bench etc)
• Fix bugs.
• While we retain our general preference for reasonably elegant code over truly horrific kludges, an only slightly horrific kludge might still be appropriate if the elegant fix touches a lot of code or is otherwise likely to be destabilising. This is always a judgement call: please send proposed patches to the mailing list for discussion.
• Don't add new features. These can wait (probably) until the next release.

This page is linked from: index  

CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively