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

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new d2ef144  Site checkin for project PLC4X: Jenkins Tools
d2ef144 is described below

commit d2ef144321995edfba58428492b6967181c1976a
Author: jenkins <[email protected]>
AuthorDate: Tue May 21 17:54:01 2019 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 developers/release.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/developers/release.html b/developers/release.html
index 21a9410..1ef3691 100644
--- a/developers/release.html
+++ b/developers/release.html
@@ -389,7 +389,7 @@ Bug Fixes
   <div class="sect2"> 
    <h3 id="_toc_preparing_a_release1">Preparing a release</h3> 
    <div class="paragraph"> 
-    <p>In order to prepare a release-candidate, the first step is switching to 
the corresponding release-branch.</p> 
+    <p>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.</p> 
    </div> 
    <div class="paragraph"> 
     <p>After that, the following command will to all preparation steps for the 
release:</p> 

Reply via email to