You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@plc4x.apache.org by cd...@apache.org on 2019/05/21 16:38:15 UTC

[plc4x] branch rel/0.4 updated: Added some more documentation to the release documentation.

This is an automated email from the ASF dual-hosted git repository.

cdutz pushed a commit to branch rel/0.4
in repository https://gitbox.apache.org/repos/asf/plc4x.git


The following commit(s) were added to refs/heads/rel/0.4 by this push:
     new 1b8b993  Added some more documentation to the release documentation.
1b8b993 is described below

commit 1b8b993a96db8a9d6a66f209b7ca9c984ca381b3
Author: Christofer Dutz <ch...@c-ware.de>
AuthorDate: Tue May 21 18:38:09 2019 +0200

    Added some more documentation to the release documentation.
---
 src/site/asciidoc/developers/release.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/site/asciidoc/developers/release.adoc b/src/site/asciidoc/developers/release.adoc
index fe02415..af57f42 100644
--- a/src/site/asciidoc/developers/release.adoc
+++ b/src/site/asciidoc/developers/release.adoc
@@ -157,6 +157,8 @@ Changes should either be re applied in `develop` or `cherry-picked`, however mer
 
 === Preparing a release
 
+As especially when switching a lot between different branches, it is recommended to do a clean checkout of the repository.
+Otherwise a lot of directories can be left over, which would be included in the source-release zip.
 In order to prepare a release-candidate, the first step is switching to the corresponding release-branch.
 
 After that, the following command will to all preparation steps for the release: