cmucl issueshttps://gitlab.common-lisp.net/cmucl/cmucl/-/issues2023-05-29T13:50:55Zhttps://gitlab.common-lisp.net/cmucl/cmucl/-/issues/231Clean up release template file2023-05-29T13:50:55ZRaymond ToyClean up release template fileThe recently added [release-template.md](src/general-info/release-template.md) is a template for release notes. Some of the items seems redundant and I'm not really sure what the difference is anymore. These seem redundant:
- ANSI comp...The recently added [release-template.md](src/general-info/release-template.md) is a template for release notes. Some of the items seems redundant and I'm not really sure what the difference is anymore. These seem redundant:
- ANSI compliance fixes
- Bug fixes
- Gitlab tickets
Perhaps we should only have "Gitlab tickets". Maybe keep "ANSI compliance fixes" if we really want to highlight that, but then it's not clear if we duplicate issue numbers here and in "Gitlab tickets".
I don't remember what "Known issues" is for; we have a bug tracker now. I guess "Feature enhancements" are for new, larger changes that we want to emphasize that isn't adequately explained in the issue list.https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/232Add wiki entry for how to create a downloadable patch2024-02-20T00:35:38ZRaymond ToyAdd wiki entry for how to create a downloadable patchA long time ago we used to support downloadable patches that could be installed in a running lisp. IIRC, you would download the patch, and add it to your init file to be loaded on startup.
Per https://gitlab.common-lisp.net/cmucl/cmucl...A long time ago we used to support downloadable patches that could be installed in a running lisp. IIRC, you would download the patch, and add it to your init file to be loaded on startup.
Per https://gitlab.common-lisp.net/cmucl/cmucl/-/issues/230#note_12088, we should revive this feature and document how to do it.