aboutsummaryrefslogtreecommitdiff
path: root/docs/markdown
diff options
context:
space:
mode:
authorJussi Pakkanen <jpakkane@gmail.com>2019-03-10 16:28:57 +0200
committerJussi Pakkanen <jpakkane@gmail.com>2019-03-10 18:40:27 +0200
commit5a4defadab29ace322b1457cc0598c06c73a2f5c (patch)
treee975007e9b4e24c4fdb5178f975dec3811dc6e76 /docs/markdown
parent7589471978301606e698626b13ef9b62638c4ea7 (diff)
downloadmeson-5a4defadab29ace322b1457cc0598c06c73a2f5c.zip
meson-5a4defadab29ace322b1457cc0598c06c73a2f5c.tar.gz
meson-5a4defadab29ace322b1457cc0598c06c73a2f5c.tar.bz2
Generate release notes from snippets automatically. [skip ci]
Diffstat (limited to 'docs/markdown')
-rw-r--r--docs/markdown/Release-notes-for-0.49.0.md2
-rw-r--r--docs/markdown/Release-notes-for-0.50.0.md25
2 files changed, 2 insertions, 25 deletions
diff --git a/docs/markdown/Release-notes-for-0.49.0.md b/docs/markdown/Release-notes-for-0.49.0.md
index 4ed4be2..9889a39 100644
--- a/docs/markdown/Release-notes-for-0.49.0.md
+++ b/docs/markdown/Release-notes-for-0.49.0.md
@@ -3,6 +3,8 @@ title: Release 0.49
short-description: Release notes for 0.49
...
+# New features
+
## Libgcrypt dependency now supports libgcrypt-config
Earlier, `dependency('libgcrypt')` could only detect the library with pkg-config
diff --git a/docs/markdown/Release-notes-for-0.50.0.md b/docs/markdown/Release-notes-for-0.50.0.md
deleted file mode 100644
index a08edfb..0000000
--- a/docs/markdown/Release-notes-for-0.50.0.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Release 0.50
-short-description: Release notes for 0.49 (preliminary)
-...
-
-# New features
-
-This page is a placeholder for the eventual release notes.
-
-Notable new features should come with release note updates. This is
-done by creating a file snippet called `snippets/featurename.md` and
-whose contents should look like this:
-
- ## Feature name
-
- A short description explaining the new feature and how it should be used.
-
-## custom_target: install no longer overrides build_by_default
-
-Earlier, if `build_by_default` was set to false and `install` was set to true in
-a `custom_target`, `install` would override it and the `custom_target` would
-always be built by default.
-Now if `build_by_default` is explicitly set to false it will no longer be
-overridden. If `build_by_default` is not set, its default will still be
-determined by the value of `install` for greater backward compatibility.