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/bookkeeper.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 6c6dfd0  Updated site at revision 35c9640
6c6dfd0 is described below

commit 6c6dfd0041e1a68dd67451db6b32385ac6888c49
Author: jenkins <[email protected]>
AuthorDate: Mon Feb 25 06:16:54 2019 +0000

    Updated site at revision 35c9640
---
 content/community/contributing/index.html | 2 +-
 content/community/issue-report/index.html | 2 +-
 content/community/meeting/index.html      | 2 +-
 content/community/releases/index.html     | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/community/contributing/index.html 
b/content/community/contributing/index.html
index ec61259..b49cad2 100644
--- a/content/community/contributing/index.html
+++ b/content/community/contributing/index.html
@@ -368,7 +368,7 @@ participate on the documentation effort.</p>
 
 <p>To avoid potential frustration during the code review cycle, we encourage 
you to clearly scope and design non-trivial contributions with the BookKeeper 
community before you start coding.</p>
 
-<p>We are using <a 
href="https://cwiki.apache.org/confluence/display/BOOKKEEPER/BookKeeper+Proposals";>BookKeeper
 Proposals</a> for managing major changes to BookKeeper.</p>
+<p>We are using <a 
href="http://bookkeeper.apache.org/community/bookkeeper_proposals/";>BookKeeper 
Proposals</a> for managing major changes to BookKeeper.</p>
 
 <h2 id="code">Code</h2>
 
diff --git a/content/community/issue-report/index.html 
b/content/community/issue-report/index.html
index 7334700..bf46d50 100644
--- a/content/community/issue-report/index.html
+++ b/content/community/issue-report/index.html
@@ -293,7 +293,7 @@ Be aware that resolving your issue may require <strong>your 
participation</stron
   <li>Please describe the feature you are requesting.</li>
   <li>Indicate the importance of this issue to you (<em>blocker</em>, 
<em>must-have</em>, <em>should-have</em>, <em>nice-to-have</em>). Are you 
currently using any workarounds to address this issue?</li>
   <li>Provide any additional detail on your proposed use case for this 
feature.</li>
-  <li>If it is a <a 
href="https://cwiki.apache.org/confluence/display/BOOKKEEPER/BookKeeper+Proposals";>BookKeeper
 Proposal</a>, please label this issue as <code 
class="highlighter-rouge">BP</code>.</li>
+  <li>If it is a <a 
href="http://bookkeeper.apache.org/community/bookkeeper_proposals/";>BookKeeper 
Proposal</a>, please label this issue as <code 
class="highlighter-rouge">BP</code>.</li>
 </ul>
 
 <h4 id="if-it-is-a-bug-report">If it is a <strong>BUG REPORT</strong></h4>
diff --git a/content/community/meeting/index.html 
b/content/community/meeting/index.html
index 5224746..508dd69 100644
--- a/content/community/meeting/index.html
+++ b/content/community/meeting/index.html
@@ -267,7 +267,7 @@
 <p>The meeting is typically comprised of 3 parts:</p>
 
 <ul>
-  <li>Discuss <a 
href="https://cwiki.apache.org/confluence/display/BOOKKEEPER/BookKeeper+Proposals";>BookKeeper
 Proposals</a>.</li>
+  <li>Discuss <a 
href="http://bookkeeper.apache.org/community/bookkeeper_proposals/";>BookKeeper 
Proposals</a>.</li>
   <li>Review and address concerns for any open pull requests.</li>
   <li>Open discussion.</li>
 </ul>
diff --git a/content/community/releases/index.html 
b/content/community/releases/index.html
index 7632780..6c5af17 100644
--- a/content/community/releases/index.html
+++ b/content/community/releases/index.html
@@ -270,7 +270,7 @@
 
 <ul>
   <li>A month before the release date, the release manager will cut branches 
and also publish a list of features that will be included in the release. These 
features will typically
-  be <a 
href="https://cwiki.apache.org/confluence/display/BOOKKEEPER/BookKeeper+Proposals";>BookKeeper
 Proposals</a>, but not always.</li>
+  be <a 
href="http://bookkeeper.apache.org/community/bookkeeper_proposals/";>BookKeeper 
Proposals</a>, but not always.</li>
   <li>Another week will be left for <em>minor</em> features to get in, but at 
this point the community will start efforts to stabilize the release branch and 
contribute mostly tests and fixes.</li>
   <li>Two weeks before the release date, the bookkeeper community will 
announce code-freeze and start rolling out release candidates, after which only 
fixes for blocking bugs will be merged.</li>
 </ul>

Reply via email to