LLM inference in C/C++
C++ ggml
llama.cpp : bump version to 0.6.0 (#29997)
Georgi Gerganovd81235049384
diff --git a/CMakeLists.txt b/CMakeLists.txtindex 8a874c96e3..3086e81b19 100644--- a/CMakeLists.txt+++ b/CMakeLists.txt@@ -4,7 +4,7 @@ include(CheckIncludeFileCXX)### llama.cpp versionset(LLAMA_VERSION_MAJOR 0)-set(LLAMA_VERSION_MINOR 5)+set(LLAMA_VERSION_MINOR 6)set(LLAMA_VERSION_PATCH 0)set(LLAMA_VERSION_BASE "${LLAMA_VERSION_MAJOR}.${LLAMA_VERSION_MINOR}.${LLAMA_VERSION_PATCH}")diff --git a/scripts/make-release-summary.txt b/scripts/make-release-summary.txtindex 8e64a50990..e8a6783bfb 100644--- a/scripts/make-release-summary.txt+++ b/scripts/make-release-summary.txt@@ -44,10 +44,12 @@ Write a summary of the change log in a few sections: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-- Combine related topics (a full list of commits will be appended independently at end of the summary)+- 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`.