From 81cccbcd0883a54f207e9d0ce0234df0087f43d5 Mon Sep 17 00:00:00 2001 From: Tomasz Gromadzki Date: Thu, 24 Aug 2023 16:01:38 +0200 Subject: [PATCH] doc: rename 1.14.0 to 2.0.0 The next major version after 1.13 is 2.0 instead of 1.14. Signed-off-by: Tomasz Gromadzki --- ChangeLog | 2 +- RELEASE_STEPS.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index cf1230bad0d..ce904357b05 100644 --- a/ChangeLog +++ b/ChangeLog @@ -85,7 +85,7 @@ Wed Apr 26 2023 Łukasz Stolarczuk Known issues: - The latest validation cycle exposed previously unknown persistency issues related to pmem2 async functions (DEPRECATED) and miniasync (EXPERIMENTAL): - #5596 and #5597. Both will be removed in the PMDK 1.14 release. These issues + #5596 and #5597. Both will be removed in the PMDK 2.0 release. These issues do NOT affect any other PMDK library. Tue Aug 25 2022 Łukasz Plewa diff --git a/RELEASE_STEPS.md b/RELEASE_STEPS.md index 37948162262..edae64c4a3a 100644 --- a/RELEASE_STEPS.md +++ b/RELEASE_STEPS.md @@ -9,8 +9,8 @@ of the PMDK repository. The second commit is required to restore a "default" sta As a helper you can export these 2 variables in your bash - with proper version set: ```bash -export VERSION=1.14.0-rc1 # the full version of the new release; -rc1 included just as an example -export VER=1.14 # the major+minor only version +export VERSION=2.0.1-rc1 # the full version of the new release; -rc1 included just as an example +export VER=2.0 # the major+minor only version ``` ## 1. Make a release locally