Buckets:
| Take a look at the changelog between the current version and the previous version - use the `./scripts/make-release-desc.sh [current-version]` to obtain it. | |
| Write a summary of the change log in a few sections: | |
| ``` | |
| ## Overview | |
| [a single paragraph overview of all changes] | |
| ### Highlights (if applicable) | |
| [go through all Pull Requests and write short summaries of those that have the "highlight" label] | |
| ### API changes (if applicable) | |
| [summarize any API changes to `/include/*`, `/tools/mtmd/mtmd.h` and `/tools/server`] | |
| ### New models (if applicable) | |
| [summarize new models added to the `src/models/` directory] | |
| ### Core changes (if applicable) | |
| [summarize the changes to `/src/*` | |
| ### Multi-modality changes (if applicable) | |
| [summarize the changes to `/tools/mtmd/`] | |
| ### Server changes (if applicable) | |
| [summarize the changes to `/tools/server/`] | |
| ### UI changes (if applicable) | |
| [summarize the changes to `/tools/ui/`] | |
| ### ggml changes (if applicable) | |
| [if the version has been updated, link to the respective `ggml` releases on Github, f.ex `https://github.com/ggml-org/ggml/releases/tag/v0.22.0`. for each version bump, lookup the release description and copy the summary here] | |
| ``` | |
| Guidelines: | |
| - All bullet point in the summary should be concise and rarely exceed a single line of 120 characters (excluding PR links) | |
| - Do not wrap or break lines within a bullet point or paragraph - each bullet point must fit on a single line (PR links allowed to exceed the line limit) | |
| - Avoid repeating `ggml`-specific changes - these should already be covered by the `ggml` release links | |
| - Provide PR link for each bullet point where possible | |
| - Don't add bullet point to state that there are no API changes in some module | |
| - Group similar/related items into a single bullet with multiple trailing PR links, one bullet per topic | |
| - A full list of commits will be appended independently at end of the summary, so it is not a problem to skip some less important changes | |
| - Skip minor-impact notes (e.g. "fix compile warnings", "refactored code", ...) | |
| Output just the summary in a markdown block, without any extra text. Save it to a local text file called `release-notes-vX.Y.Z.txt`. | |
Xet Storage Details
- Size:
- 2.18 kB
- Xet hash:
- a08a3079fb1cbd4a6d8376c612af67bab9fdeb23a46ae5fde398d3c4ee787b4d
·
Xet efficiently stores files, intelligently splitting them into unique chunks and accelerating uploads and downloads. More info.