[sling-site] branch master updated: Note about possible jenkins failure if fresh modules are added to sling-starter

[st...@apache.org]

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

stefanegli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new f02720d  Note about possible jenkins failure if fresh modules are added to sling-starter
f02720d is described below

commit f02720d8ad14ee34cf36d3371d0aa9d136212efb
Author: Stefan Egli <st...@apache.org>
AuthorDate: Mon Apr 19 15:48:09 2021 +0200

    Note about possible jenkins failure if fresh modules are added to sling-starter
---
 src/main/jbake/content/documentation/development/release-management.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index de159d4..b7ee2eb 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -256,6 +256,8 @@ Close all issues associated with the released version.
 If the released module was already included in the Sling Starter, or if a new release should be included in it,
 update the [Starter Module](https://github.com/apache/sling-org-apache-sling-starter)'s feature model accordingly.
 
+Please note that this might fail the jenkins if a newly uploaded artifact is not yet mirrored.
+
 ## Create an Announcement
 
 We usually do such announcements only for "important" releases, as opposed to small individual module