Overhauled the section 'Prepare the release notes'.
Project: http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/commit/d18f716a Tree: http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/tree/d18f716a Diff: http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/diff/d18f716a Branch: refs/heads/overhauling-release-guide Commit: d18f716aae54e7636bf8759fd045135079887944 Parents: c6b6377 Author: Oliver B. Fischer <ple...@apache.org> Authored: Sat Jul 8 23:58:27 2017 +0200 Committer: Oliver B. Fischer <ple...@apache.org> Committed: Sat Jul 8 23:58:27 2017 +0200 ---------------------------------------------------------------------- content/release-guide.adoc | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-tamaya-site/blob/d18f716a/content/release-guide.adoc ---------------------------------------------------------------------- diff --git a/content/release-guide.adoc b/content/release-guide.adoc index 9a7eb28..b0ba895 100644 --- a/content/release-guide.adoc +++ b/content/release-guide.adoc @@ -80,18 +80,32 @@ actual release process. .. if the issue can be postponed for the next release .. how long it takes to resolve it and if someone can help. + +== Prepare the release notes + +* Create release notes and commit them to the `/readme/` + directory of the project. The file name of the release + notes document should be `ReleaseNotes-[version].html`. + +# Question: How to handle the problem that we actually have +# to distributions? One is API&Core and the second is the +# extension distribution? At the moment the release notes +# are part of API&Core. The Extensions contain only a +# reference to API&Core +# Oliver B. Fischer, 2017-07-08 +# --- Rewritten until here --- -== Prepare the release -* Create release notes and commit them to `tamaya/readme/` (format `ReleaseNotes-[version].html`) + * Create a release branch in git and switch to this branch: + === Using the Release Plugin For performing the release you can use the maven release plugin:
