date:20170805

[GitHub] jvrao commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

jvrao commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131532316
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] jvrao commented on issue #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

jvrao commented on issue #398: Issue 397: [CI] publish-website job failed when 
mvn:release bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/pull/398#issuecomment-320478958
 
 
   LGTM +1 
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] zhaijack commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

2017-08-05 Thread git

zhaijack commented on a change in pull request #342: Issue 338: add first draft 
Docker image including community suggestions
URL: https://github.com/apache/bookkeeper/pull/342#discussion_r131532262
 
 

 ##
 File path: docker/Dockerfile
 ##
 @@ -0,0 +1,58 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+FROM centos:7
+MAINTAINER Apache BookKeeper 
+
+ARG BK_VERSION=4.4.0
+ARG DISTRO_NAME=bookkeeper-server-${BK_VERSION}-bin
+ARG GPG_KEY=B3D56514
+
+ENV BOOKIE_PORT=3181
+EXPOSE $BOOKIE_PORT
+ENV BK_USER=bookkeeper
+
+# Download Apache Bookkeeper, untar and clean up
+RUN set -x \
+&& adduser "${BK_USER}" \
+&& yum install -y java-1.8.0-openjdk-headless wget bash python md5sum 
sha1sum \
+&& mkdir -pv /opt \
+&& cd /opt \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.asc";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.md5";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.sha1";
 \
+&& md5sum -c ${DISTRO_NAME}.tar.gz.md5 \
+&& sha1sum -c ${DISTRO_NAME}.tar.gz.sha1 \
+&& gpg --keyserver ha.pool.sks-keyservers.net --recv-key "$GPG_KEY" \
+&& gpg --batch --verify "$DISTRO_NAME.tar.gz.asc" "$DISTRO_NAME.tar.gz" \
+&& tar -xzf "$DISTRO_NAME.tar.gz" \
+&& mv bookkeeper-server-${BK_VERSION}/ /opt/bookkeeper/ \
+&& rm -rf "$DISTRO_NAME.tar.gz" "$DISTRO_NAME.tar.gz.asc" 
"$DISTRO_NAME.tar.gz.md5" "$DISTRO_NAME.tar.gz.sha1" \
+&& yum remove -y wget \
+&& yum clean all
+
+WORKDIR /opt/bookkeeper
+
+COPY scripts/apply-config-from-env.py scripts/entrypoint.sh 
scripts/healthcheck.sh /opt/bookkeeper/
+
+ENTRYPOINT [ "/bin/bash", "/opt/bookkeeper/entrypoint.sh" ]
+CMD ["/opt/bookkeeper/bin/bookkeeper", "bookie"]
 
 Review comment:
   Yes. Thanks for clarification
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] merlimat closed pull request #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

merlimat closed pull request #398: Issue 397: [CI] publish-website job failed 
when mvn:release bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/pull/398
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] merlimat closed issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

merlimat closed issue #397: [CI] publish-website job failed when mvn:release 
bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/issues/397
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sijie opened a new issue #399: BookKeeperDiskSpaceWeightedLedgerPlacementTest.testDiskSpaceWeightedBookieSelectionWithBookiesDying failed

2017-08-05 Thread git

sijie opened a new issue #399: 
BookKeeperDiskSpaceWeightedLedgerPlacementTest.testDiskSpaceWeightedBookieSelectionWithBookiesDying
 failed
URL: https://github.com/apache/bookkeeper/issues/399
 
 
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do?
   
   ci job ran
   
   - What did you expect to see?
   
   ci passed
   
   - What did you see instead?
   
   ```
   java.lang.AssertionError: Weigheted placement is not honored1
at 
org.apache.bookkeeper.client.BookKeeperDiskSpaceWeightedLedgerPlacementTest.testDiskSpaceWeightedBookieSelectionWithBookiesDying(BookKeeperDiskSpaceWeightedLedgerPlacementTest.java:330)
   ```
   
   
https://builds.apache.org/job/bookkeeper-release-nightly-snapshot/org.apache.bookkeeper$bookkeeper-server/7/testReport/junit/org.apache.bookkeeper.client/BookKeeperDiskSpaceWeightedLedgerPlacementTest/testDiskSpaceWeightedBookieSelectionWithBookiesDying/
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Jenkins build is unstable: bookkeeper-release-nightly-snapshot #7

2017-08-05 Thread Apache Jenkins Server

See

[GitHub] sijie opened a new pull request #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

sijie opened a new pull request #398: Issue 397: [CI] publish-website job 
failed when mvn:release bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/pull/398
 
 
   Descriptions of the changes in this PR:
   
   Use `mvn install` rather than `mvn compile`
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sijie commented on issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

sijie commented on issue #397: [CI] publish-website job failed when mvn:release 
bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/issues/397#issuecomment-320470689
 
 
   The problem is because `javadoc-gen.sh` uses `mvn compile javadoc` to 
generate the javadoc. if the artifacts were cached, it is totally fine. but 
when we bump the version from 4.5.0 to 4.6.0, there are not `4.6.0` artifacts 
cached locally. so we need to change it to use `mvn clean install` instead.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sijie opened a new issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

2017-08-05 Thread git

sijie opened a new issue #397: [CI] publish-website job failed when mvn:release 
bump version to 4.6.0-SNAPSHOT
URL: https://github.com/apache/bookkeeper/issues/397
 
 
   
   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do?
   
   ci runs publish-website job when a change is merge to master. the change was 
from `mvn release` to bump the version from 4.5.0 to 4.6.0
   
   - What did you expect to see?
   
   publish-website job should run as expected.
   
   - What did you see instead?
   
   publish-website job failed due to
   
   ```
   [ERROR] Failed to execute goal on project bookkeeper-benchmark: Could not 
resolve dependencies for project 
org.apache.bookkeeper:bookkeeper-benchmark:jar:4.6.0-SNAPSHOT: Could not find 
artifact org.apache.bookkeeper:bookkeeper-server:jar:tests:4.6.0-SNAPSHOT in 
Nexus (http://repository.apache.org/snapshots) -> [Help 1]
   ```
   
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: [Draft] bookkeeper board report - August 2017

2017-08-05 Thread Sijie Guo

LGTM +1.



On Tue, Aug 1, 2017 at 12:59 AM, Jia Zhai  wrote:

> Hi all,
> Here is a draft for our August report,  Please help review and comments on
> it.
>
> Thanks a lot.
> -Jia
>
> ==
> ## Description:
>
> BookKeeper is a distributed, reliable, and high performance
> logging service. It has been used as a fundamental service to build
> high available and replicated services in companies like Twitter,
> Yahoo and Salesforce. It is also the log segment store for Apache
> DistributedLog (incubating) and message store for Yahoo Pulsar.
>
> ## Issues:
>
> There are no issues requiring board attention at this time.
>
> ## Activity:
>
> - DistributedLog graduates as a sub-project of BookKeeper. Consolidate the
> development with log stream library over bookkeeper.
> - BookKeeper moves the development to github - use github for tracking
> issues, moved to gitbox.
> - New contributions for a new bookkeeper website.
>
> ## Health report:
>
> - After a year of development among developers from multiple different
> companies, the 4.5 release is also there. It is due in this August, it
> includes exciting features like security support, netty 4 upgrade,
> weight-based placement policy, long poll reads.
> - We moved to gitbox to reduce the gap for new contributors to engage with
> the community.
> - DL graduates as a sub-project to consolidate the development efforts
> around log stream library.
>
> ## PMC changes:
>
>  - Currently 9 PMC members.
>  - JV Jujjuri was added to the PMC on Tue Jun 27 2017
>
> ## Committer base changes:
>
>  - Currently 14 committers.
>  - No new committers added in the last 3 months
>  - Last committers addition was Enrico Olivelli and Charan Reddy G at Mar
> 2017
>
> ## Releases:
>
>  - Last release was 4.4.0 on Sun May 15 2016
>
> ## Mailing list activity:
>
> Consolidate efforts coming from DL graduation as sub-project. More
> contributor/committer engagement cause the increased of mailing list
> activities.
>
>  - dev@bookkeeper.apache.org:
> - 90 subscribers (up 7 in the last 3 months):
> - 2706 emails sent to list (875 in previous quarter)
>
>  - iss...@bookkeeper.apache.org:
> - 6 subscribers (up 0 in the last 3 months)
>
>  - u...@bookkeeper.apache.org:
> - 100 subscribers (down -1 in the last 3 months):
> - 27 emails sent to list (23 in previous quarter)
>
>
> ## JIRA activity:
>  - 60 JIRA tickets created in the last 3 months
>  - 88 JIRA tickets closed/resolved in the last 3 months
>
>  - 85 Github issues created in the last 3 months
>  - 42 Github issues closed/resolved in the last 3 months
>  - 83 Github Pull Requests created in the last 3 months
>  - 75 Github Pull Requests closed/resolved in the last 3 months
>

Re: release 4.5

2017-08-05 Thread Enrico Olivelli

Il sab 5 ago 2017, 21:55 Sijie Guo  ha scritto:

> Updates (from JV and me)
>
> - branch 4.5 is created (JV) :
> https://github.com/apache/bookkeeper/tree/branch-4.5
> - master is bumped to 4.6.0-SNAPSHOT (JV)
> - CI is back to normal after skipping running code coverage (sijie)
>
> Committers,
>
> New changes are okay to merge to master now. If a change needs to be in
> 4.5, please also cherry-pick to 4.5 following the instructions promoted in
> `dev/bk-merge-pr.py`.
>
> Next Steps:
>
> JV and me attempted to create a release candidate. However we have a
> problem to publish the artifacts to the staging. It pushed directly to the
> snapshots. I doubt it is something related to the changes Enrico made for
> publishing to snapshots. Will investigate and figure out how to do that.


Actually I did not change anything in order to push snapshots. It is the
standard maven workflow:
The deploy goal deploys to the snapshots repository if the version ends
with -snapshot
It deploys to the relase repository otherwise.
The only real change was to update the apache parent pom, with drives the
whole deploy process

Hope that help
Enrico


Expect a release candidate come out soon.
>
> - Sijie
>
-- 


-- Enrico Olivelli

Re: release 4.5

2017-08-05 Thread Sijie Guo

+ Enrico

On Sat, Aug 5, 2017 at 12:55 PM, Sijie Guo  wrote:

> Updates (from JV and me)
>
> - branch 4.5 is created (JV) : https://github.com/apache/
> bookkeeper/tree/branch-4.5
> - master is bumped to 4.6.0-SNAPSHOT (JV)
> - CI is back to normal after skipping running code coverage (sijie)
>
> Committers,
>
> New changes are okay to merge to master now. If a change needs to be in
> 4.5, please also cherry-pick to 4.5 following the instructions promoted in
> `dev/bk-merge-pr.py`.
>
> Next Steps:
>
> JV and me attempted to create a release candidate. However we have a
> problem to publish the artifacts to the staging. It pushed directly to the
> snapshots. I doubt it is something related to the changes Enrico made for
> publishing to snapshots. Will investigate and figure out how to do that.
> Expect a release candidate come out soon.
>
> - Sijie
>

Re: Jenkins build is back to stable : bookkeeper-master #1843

2017-08-05 Thread Enrico Olivelli

Il sab 5 ago 2017, 21:45 Sijie Guo  ha scritto:

> I changed the CI job to skip running code coverage. it seems to be stable.
> I doubt a lot of weird behavior on CI builds related to the code coverage
> run. for now, I am going skip code coverage on all the ci jobs to make it
> stable again.
>

My bad!
I left the prototype of code coverage tool running on the master job! This
is the explanation of all of the classloading errors. Code coverage tools
run by rewriting byte code, cobertura does not run with java8 very well.
When I will be back in that task, after the 4.5  release I will create an
independent job.
Thank you Sijie

Enrico

> - Sijie
>
> On Sat, Aug 5, 2017 at 11:10 AM, Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> See <
>> https://builds.apache.org/job/bookkeeper-master/1843/display/redirect>
>>
>>
> --

-- Enrico Olivelli

release 4.5

2017-08-05 Thread Sijie Guo

Updates (from JV and me)

- branch 4.5 is created (JV) :
https://github.com/apache/bookkeeper/tree/branch-4.5
- master is bumped to 4.6.0-SNAPSHOT (JV)
- CI is back to normal after skipping running code coverage (sijie)

Committers,

New changes are okay to merge to master now. If a change needs to be in
4.5, please also cherry-pick to 4.5 following the instructions promoted in
`dev/bk-merge-pr.py`.

Next Steps:

JV and me attempted to create a release candidate. However we have a
problem to publish the artifacts to the staging. It pushed directly to the
snapshots. I doubt it is something related to the changes Enrico made for
publishing to snapshots. Will investigate and figure out how to do that.
Expect a release candidate come out soon.

- Sijie

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131528043
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527429
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527628
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527584
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527589
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527662
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

2017-08-05 Thread git

sijie commented on a change in pull request #305: Issue 305: New Release Guide
URL: https://github.com/apache/bookkeeper/pull/305#discussion_r131527602
 
 

 ##
 File path: site/community/release_guide.md
 ##
 @@ -0,0 +1,475 @@
+# Apache BookKeeper Release Guide
+
+* TOC
+{:toc}
+
+This page documents the procedure to make an Apache BookKeeper release.
+
+## Introduction
+
+The Apache BookKeeper project periodically declares and publishes releases. A 
release is one or more packages of the project artifact(s) that are approved 
for general public distribution and use. They may come with various degrees of 
caveat regarding their perceived quality and potential for change, such as 
?alpha?, ?beta?, ?incubating?, ?stable?, etc.
+
+The BookKeeper community treats releases with great importance. They are a 
public face of the project and most users interact with the project only 
through the releases. Releases are signed off by the entire BookKeeper 
community in a public vote.
+
+Each release is executed by a *Release Manager*, who is selected among the 
[BookKeeper committers](http://bookkeeper.apache.org/credits.html). This 
document describes the process that the Release Manager follows to perform a 
release. Any changes to this process should be discussed and adopted on the 
[dev@ mailing list](http://bookkeeper.apache.org/lists.html).
+
+Please remember that publishing software has legal consequences. This guide 
complements the foundation-wide [Product Release 
Policy](http://www.apache.org/dev/release.html) and [Release Distribution 
Policy](http://www.apache.org/dev/release-distribution).
+
+## Overview
+
+The release process consists of several steps:
+
+1. Decide to release
+2. Prepare for the release
+3. Build a release candidate
+4. Vote on the release candidate
+5. If necessary, fix any issues and go back to step 3.
+6. Finalize the release
+7. Promote the release
+
+**
+
+## Decide to release
+
+Deciding to release and selecting a Release Manager is the first step of the 
release process. This is a consensus-based decision of the entire community.
+
+Anybody can propose a release on the dev@ mailing list, giving a solid 
argument and nominating a committer as the Release Manager (including 
themselves). There?s no formal process, no vote requirements, and no timing 
requirements. Any objections should be resolved by consensus before starting 
the release.
+
+In general, the community prefers to have a rotating set of 3-5 Release 
Managers. Keeping a small core set of managers allows enough people to build 
expertise in this area and improve processes over time, without Release 
Managers needing to re-learn the processes for each release. That said, if you 
are a committer interested in serving the community in this way, please reach 
out to the community on the dev@ mailing list.
+
+### Checklist to proceed to the next step
+
+1. Community agrees to release
+2. Community selects a Release Manager
+
+**
+
+## Prepare for the release
+
+Before your first release, you should perform one-time configuration steps. 
This will set up your security keys for signing the release and access to 
various release repositories.
+
+To prepare for each release, you should audit the project status both in the 
JIRA issue tracker and the Github issue tracker, and do necessary bookkeeping. 
Finally, you should create a release branch from which individual release 
candidates will be built.
+
+### One-time setup instructions
+
+ GPG Key
+
+You need to have a GPG key to sign the release artifacts. Please be aware of 
the ASF-wide [release signing 
guidelines](https://www.apache.org/dev/release-signing.html). If you don?t have 
a GPG key associated with your Apache account, please create one according to 
the guidelines.
+
+Determine your Apache GPG Key and Key ID, as follows:
+
+gpg --list-keys
+
+This will list your GPG keys. One of these should reflect your Apache account, 
for example:
+
+--
+pub   2048R/845E6689 2016-02-23
+uid  Nomen Nescio 
+sub   2048R/BA4D50BE 2016-02-23
+
+Here, the key ID is the 8-digit hex string in the `pub` line: `845E6689`.
+
+Now, add your Apache GPG key to the BookKeeper?s `KEYS` file in 
[`dist`](https://svn.apache.org/repos/asf/bookkeeper/dist/KEYS). Follow the 
instructions listed at the top of these files.
+
+Configure `git` to use this key when signing code by giving it your key ID, as 
follows:
+
+git config --global user.signingkey 845E6689
+
+You may drop the `--global` option if you?d prefer to use this key for the 
current repository only.
+
+You may wish to start `gpg-agent` to unlock your GPG key only once using your 
passphrase. Otherwise, you may need to enter this passphrase hundreds of times. 
The setup for `gpg-agent` varies based on operating system, but may be 
something like this:
+
+eval $(gpg-agent --daemon --no-grab --write-env-file $HO

Re: Jenkins build is back to stable : bookkeeper-master #1843

2017-08-05 Thread Sijie Guo

I changed the CI job to skip running code coverage. it seems to be stable.
I doubt a lot of weird behavior on CI builds related to the code coverage
run. for now, I am going skip code coverage on all the ci jobs to make it
stable again.

- Sijie

On Sat, Aug 5, 2017 at 11:10 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See  >
>
>

[GitHub] sijie commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

2017-08-05 Thread git

sijie commented on a change in pull request #342: Issue 338: add first draft 
Docker image including community suggestions
URL: https://github.com/apache/bookkeeper/pull/342#discussion_r131528056
 
 

 ##
 File path: docker/Dockerfile
 ##
 @@ -0,0 +1,58 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+FROM centos:7
+MAINTAINER Apache BookKeeper 
+
+ARG BK_VERSION=4.4.0
+ARG DISTRO_NAME=bookkeeper-server-${BK_VERSION}-bin
+ARG GPG_KEY=B3D56514
+
+ENV BOOKIE_PORT=3181
+EXPOSE $BOOKIE_PORT
+ENV BK_USER=bookkeeper
+
+# Download Apache Bookkeeper, untar and clean up
+RUN set -x \
+&& adduser "${BK_USER}" \
+&& yum install -y java-1.8.0-openjdk-headless wget bash python md5sum 
sha1sum \
+&& mkdir -pv /opt \
+&& cd /opt \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.asc";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.md5";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.sha1";
 \
+&& md5sum -c ${DISTRO_NAME}.tar.gz.md5 \
+&& sha1sum -c ${DISTRO_NAME}.tar.gz.sha1 \
+&& gpg --keyserver ha.pool.sks-keyservers.net --recv-key "$GPG_KEY" \
+&& gpg --batch --verify "$DISTRO_NAME.tar.gz.asc" "$DISTRO_NAME.tar.gz" \
+&& tar -xzf "$DISTRO_NAME.tar.gz" \
+&& mv bookkeeper-server-${BK_VERSION}/ /opt/bookkeeper/ \
+&& rm -rf "$DISTRO_NAME.tar.gz" "$DISTRO_NAME.tar.gz.asc" 
"$DISTRO_NAME.tar.gz.md5" "$DISTRO_NAME.tar.gz.sha1" \
+&& yum remove -y wget \
+&& yum clean all
+
+WORKDIR /opt/bookkeeper
+
+COPY scripts/apply-config-from-env.py scripts/entrypoint.sh 
scripts/healthcheck.sh /opt/bookkeeper/
+
+ENTRYPOINT [ "/bin/bash", "/opt/bookkeeper/entrypoint.sh" ]
+CMD ["/opt/bookkeeper/bin/bookkeeper", "bookie"]
 
 Review comment:
   gotcha. thank you for clarification @merlimat 
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Build failed in Jenkins: bookkeeper-postcommit-publish-website #37

2017-08-05 Thread Sijie Guo

JV and me are working on cutting a 4.5. branch. This might related to that.
will take a look at this later.

- Sijie

On Sat, Aug 5, 2017 at 11:06 AM, Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See  publish-website/37/display/redirect?page=changes>
>
> Changes:
>
> [vjujjuri] [maven-release-plugin] prepare branch branch-4.5
>
> [vjujjuri] [maven-release-plugin] prepare for next development iteration
>
> --
> Started by an SCM change
> Started by an SCM change
> [EnvInject] - Loading node environment variables.
> Building remotely on H19 (git-websites) in workspace <
> https://builds.apache.org/job/bookkeeper-postcommit-publish-website/ws/>
>  > git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url https://gitbox.apache.org/
> repos/asf/bookkeeper.git # timeout=10
> Fetching upstream changes from https://gitbox.apache.org/
> repos/asf/bookkeeper.git
>  > git --version # timeout=10
> using GIT_SSH to set credentials master pub key
>  > git fetch --tags --progress https://gitbox.apache.org/
> repos/asf/bookkeeper.git +refs/heads/*:refs/remotes/origin/*
> +refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*
>  > git rev-parse origin/master^{commit} # timeout=10
> Checking out Revision 59562a7bb2b300b0706d17e9fc034d6604b71626
> (origin/master)
> Commit message: "[maven-release-plugin] prepare for next development
> iteration"
>  > git config core.sparsecheckout # timeout=10
>  > git checkout -f 59562a7bb2b300b0706d17e9fc034d6604b71626
>  > git rev-list bf1d58f197b9a99863f563ce0fdcb0e1f3483b8d # timeout=10
> Cleaning workspace
>  > git rev-parse --verify HEAD # timeout=10
> Resetting working tree
>  > git reset --hard # timeout=10
>  > git clean -fdx # timeout=10
> [bookkeeper-postcommit-publish-website] $ /bin/bash -xe /tmp/
> jenkins6023234445517054205.sh
> + export MAVEN_HOME=/home/jenkins/tools/maven/latest
> + MAVEN_HOME=/home/jenkins/tools/maven/latest
> + export PATH=/home/jenkins/tools/java/latest1.8/bin:/home/jenkins/
> tools/maven/latest/bin:/home/jenkins/tools/java/latest1.8/
> bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
> sbin:/bin:/usr/games:/usr/local/games
> + PATH=/home/jenkins/tools/java/latest1.8/bin:/home/jenkins/
> tools/maven/latest/bin:/home/jenkins/tools/java/latest1.8/
> bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/
> sbin:/bin:/usr/games:/usr/local/games
> + export MAVEN_OPTS=-Xmx2048m
> + MAVEN_OPTS=-Xmx2048m
> + cd site
> + make clean javadoc
> rm -rf _site local-generated generated_site
> scripts/javadoc-gen.sh
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache BookKeeper :: Parent
> [INFO] Apache BookKeeper :: Build Tools
> [INFO] Apache BookKeeper :: Compability Dependencies
> [INFO] Apache BookKeeper :: Compability Dependencies :: 4.0.0
> [INFO] Apache BookKeeper :: Compability Dependencies :: 4.1.0
> [INFO] Apache BookKeeper :: Compability Dependencies :: 4.2.0
> [INFO] Apache BookKeeper :: Stats API
> [INFO] Apache BookKeeper :: Server
> [INFO] Apache BookKeeper :: Benchmark
> [INFO] Apache BookKeeper :: Stats Providers :: Twitter Finagle Stats
> [INFO] Apache BookKeeper :: Stats Providers :: Twitter Science Stats
> [INFO] Apache BookKeeper :: Stats Providers :: Twitter Ostrich Stats
> [INFO] Apache BookKeeper :: Stats Providers :: Codahale Metrics
> [INFO] Apache BookKeeper :: Stats Providers :: Prometheus
> [INFO] Apache BookKeeper :: Stats Providers
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache BookKeeper :: Parent 4.6.0-SNAPSHOT
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process
> (process-resource-bundles) @ bookkeeper ---
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache BookKeeper :: Build Tools 4.6.0-SNAPSHOT
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process
> (process-resource-bundles) @ buildtools ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
> buildtools ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 5 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @
> buildtools ---
> [INFO] No sources to compile
> [INFO]
> [INFO] 
> 
> [INFO] Building Apache BookKeeper :: Compability Dependencies
> 4.6.0-SNAPSHOT
> [INFO] 
>

Jenkins build is back to stable : bookkeeper-master #1843

2017-08-05 Thread Apache Jenkins Server

See

Build failed in Jenkins: bookkeeper-postcommit-publish-website #37

2017-08-05 Thread Apache Jenkins Server

See 


Changes:

[vjujjuri] [maven-release-plugin] prepare branch branch-4.5

[vjujjuri] [maven-release-plugin] prepare for next development iteration

--
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H19 (git-websites) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://gitbox.apache.org/repos/asf/bookkeeper.git # timeout=10
Fetching upstream changes from 
https://gitbox.apache.org/repos/asf/bookkeeper.git
 > git --version # timeout=10
using GIT_SSH to set credentials master pub key
 > git fetch --tags --progress 
 > https://gitbox.apache.org/repos/asf/bookkeeper.git 
 > +refs/heads/*:refs/remotes/origin/* 
 > +refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*
 > git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 59562a7bb2b300b0706d17e9fc034d6604b71626 (origin/master)
Commit message: "[maven-release-plugin] prepare for next development iteration"
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 59562a7bb2b300b0706d17e9fc034d6604b71626
 > git rev-list bf1d58f197b9a99863f563ce0fdcb0e1f3483b8d # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
[bookkeeper-postcommit-publish-website] $ /bin/bash -xe 
/tmp/jenkins6023234445517054205.sh
+ export MAVEN_HOME=/home/jenkins/tools/maven/latest
+ MAVEN_HOME=/home/jenkins/tools/maven/latest
+ export 
PATH=/home/jenkins/tools/java/latest1.8/bin:/home/jenkins/tools/maven/latest/bin:/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+ 
PATH=/home/jenkins/tools/java/latest1.8/bin:/home/jenkins/tools/maven/latest/bin:/home/jenkins/tools/java/latest1.8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
+ export MAVEN_OPTS=-Xmx2048m
+ MAVEN_OPTS=-Xmx2048m
+ cd site
+ make clean javadoc
rm -rf _site local-generated generated_site
scripts/javadoc-gen.sh
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] Apache BookKeeper :: Parent
[INFO] Apache BookKeeper :: Build Tools
[INFO] Apache BookKeeper :: Compability Dependencies
[INFO] Apache BookKeeper :: Compability Dependencies :: 4.0.0
[INFO] Apache BookKeeper :: Compability Dependencies :: 4.1.0
[INFO] Apache BookKeeper :: Compability Dependencies :: 4.2.0
[INFO] Apache BookKeeper :: Stats API
[INFO] Apache BookKeeper :: Server
[INFO] Apache BookKeeper :: Benchmark
[INFO] Apache BookKeeper :: Stats Providers :: Twitter Finagle Stats
[INFO] Apache BookKeeper :: Stats Providers :: Twitter Science Stats
[INFO] Apache BookKeeper :: Stats Providers :: Twitter Ostrich Stats
[INFO] Apache BookKeeper :: Stats Providers :: Codahale Metrics
[INFO] Apache BookKeeper :: Stats Providers :: Prometheus
[INFO] Apache BookKeeper :: Stats Providers
[INFO] 
[INFO] 
[INFO] Building Apache BookKeeper :: Parent 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ bookkeeper ---
[INFO] 
[INFO] 
[INFO] Building Apache BookKeeper :: Build Tools 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ buildtools ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
buildtools ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 5 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ buildtools 
---
[INFO] No sources to compile
[INFO] 
[INFO] 
[INFO] Building Apache BookKeeper :: Compability Dependencies 4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ compat-deps ---
[INFO] 
[INFO] 
[INFO] Building Apache BookKeeper :: Compability Dependencies :: 4.0.0 
4.6.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:

[GitHub] merlimat commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

2017-08-05 Thread git

merlimat commented on a change in pull request #342: Issue 338: add first draft 
Docker image including community suggestions
URL: https://github.com/apache/bookkeeper/pull/342#discussion_r131526053
 
 

 ##
 File path: docker/Dockerfile
 ##
 @@ -0,0 +1,58 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+FROM centos:7
+MAINTAINER Apache BookKeeper 
+
+ARG BK_VERSION=4.4.0
+ARG DISTRO_NAME=bookkeeper-server-${BK_VERSION}-bin
+ARG GPG_KEY=B3D56514
+
+ENV BOOKIE_PORT=3181
+EXPOSE $BOOKIE_PORT
+ENV BK_USER=bookkeeper
+
+# Download Apache Bookkeeper, untar and clean up
+RUN set -x \
+&& adduser "${BK_USER}" \
+&& yum install -y java-1.8.0-openjdk-headless wget bash python md5sum 
sha1sum \
+&& mkdir -pv /opt \
+&& cd /opt \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.asc";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.md5";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.sha1";
 \
+&& md5sum -c ${DISTRO_NAME}.tar.gz.md5 \
+&& sha1sum -c ${DISTRO_NAME}.tar.gz.sha1 \
+&& gpg --keyserver ha.pool.sks-keyservers.net --recv-key "$GPG_KEY" \
+&& gpg --batch --verify "$DISTRO_NAME.tar.gz.asc" "$DISTRO_NAME.tar.gz" \
+&& tar -xzf "$DISTRO_NAME.tar.gz" \
+&& mv bookkeeper-server-${BK_VERSION}/ /opt/bookkeeper/ \
+&& rm -rf "$DISTRO_NAME.tar.gz" "$DISTRO_NAME.tar.gz.asc" 
"$DISTRO_NAME.tar.gz.md5" "$DISTRO_NAME.tar.gz.sha1" \
+&& yum remove -y wget \
+&& yum clean all
+
+WORKDIR /opt/bookkeeper
+
+COPY scripts/apply-config-from-env.py scripts/entrypoint.sh 
scripts/healthcheck.sh /opt/bookkeeper/
+
+ENTRYPOINT [ "/bin/bash", "/opt/bookkeeper/entrypoint.sh" ]
+CMD ["/opt/bookkeeper/bin/bookkeeper", "bookie"]
 
 Review comment:
   the `CMD` portion can anyway be overridden, either on CLI or when writing 
the K8S yaml spec
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sijie commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

2017-08-05 Thread git

sijie commented on a change in pull request #342: Issue 338: add first draft 
Docker image including community suggestions
URL: https://github.com/apache/bookkeeper/pull/342#discussion_r131525994
 
 

 ##
 File path: docker/Dockerfile
 ##
 @@ -0,0 +1,58 @@
+#
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+#
+
+FROM centos:7
+MAINTAINER Apache BookKeeper 
+
+ARG BK_VERSION=4.4.0
+ARG DISTRO_NAME=bookkeeper-server-${BK_VERSION}-bin
+ARG GPG_KEY=B3D56514
+
+ENV BOOKIE_PORT=3181
+EXPOSE $BOOKIE_PORT
+ENV BK_USER=bookkeeper
+
+# Download Apache Bookkeeper, untar and clean up
+RUN set -x \
+&& adduser "${BK_USER}" \
+&& yum install -y java-1.8.0-openjdk-headless wget bash python md5sum 
sha1sum \
+&& mkdir -pv /opt \
+&& cd /opt \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.asc";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.md5";
 \
+&& wget -q 
"https://archive.apache.org/dist/bookkeeper/bookkeeper-${BK_VERSION}/${DISTRO_NAME}.tar.gz.sha1";
 \
+&& md5sum -c ${DISTRO_NAME}.tar.gz.md5 \
+&& sha1sum -c ${DISTRO_NAME}.tar.gz.sha1 \
+&& gpg --keyserver ha.pool.sks-keyservers.net --recv-key "$GPG_KEY" \
+&& gpg --batch --verify "$DISTRO_NAME.tar.gz.asc" "$DISTRO_NAME.tar.gz" \
+&& tar -xzf "$DISTRO_NAME.tar.gz" \
+&& mv bookkeeper-server-${BK_VERSION}/ /opt/bookkeeper/ \
+&& rm -rf "$DISTRO_NAME.tar.gz" "$DISTRO_NAME.tar.gz.asc" 
"$DISTRO_NAME.tar.gz.md5" "$DISTRO_NAME.tar.gz.sha1" \
+&& yum remove -y wget \
+&& yum clean all
+
+WORKDIR /opt/bookkeeper
+
+COPY scripts/apply-config-from-env.py scripts/entrypoint.sh 
scripts/healthcheck.sh /opt/bookkeeper/
+
+ENTRYPOINT [ "/bin/bash", "/opt/bookkeeper/entrypoint.sh" ]
+CMD ["/opt/bookkeeper/bin/bookkeeper", "bookie"]
 
 Review comment:
   I am wondering if you should auto-start the bookie in the docker image. it 
might be more flexible if we don't auto-start the bookie, and defer that 
deployment methods like dcos and k8s.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Jenkins build is still unstable: bookkeeper-master #1842

2017-08-05 Thread Apache Jenkins Server

See

[GitHub] jiazhai closed issue #390: Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

2017-08-05 Thread git

jiazhai closed issue #390: Test errors in 
TestRackawareEnsemblePlacementPolicyUsingScript
URL: https://github.com/apache/bookkeeper/issues/390
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] jiazhai closed pull request #396: Issue 390: [CI] Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

2017-08-05 Thread git

jiazhai closed pull request #396: Issue 390: [CI] Test errors in 
TestRackawareEnsemblePlacementPolicyUsingScript
URL: https://github.com/apache/bookkeeper/pull/396
 
 
   
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] zhaijack commented on issue #396: Issue 390: [CI] Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

2017-08-05 Thread git

zhaijack commented on issue #396: Issue 390: [CI] Test errors in 
TestRackawareEnsemblePlacementPolicyUsingScript
URL: https://github.com/apache/bookkeeper/pull/396#issuecomment-320430028
 
 
   tests passed, will shipit. ?
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sijie opened a new pull request #396: Issue 390: Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

2017-08-05 Thread git

sijie opened a new pull request #396: Issue 390: Test errors in 
TestRackawareEnsemblePlacementPolicyUsingScript
URL: https://github.com/apache/bookkeeper/pull/396
 
 
   Descriptions of the changes in this PR:
   
   `Shell` class was ported from hadoop, but it contains a lot of unused code. 
Especially there is not `HADOOP_HOME` will set, so an exception will be thrown. 
(although the issue seems to be hidden in mac)
   
   This change is to clean up the `Shell` class. The `Shell` class is only used 
for executing shell script configured in rackaware placement policy.
 

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] jvrao commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] jvrao commented on issue #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

[GitHub] zhaijack commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

[GitHub] merlimat closed pull request #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

[GitHub] merlimat closed issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

[GitHub] sijie opened a new issue #399: BookKeeperDiskSpaceWeightedLedgerPlacementTest.testDiskSpaceWeightedBookieSelectionWithBookiesDying failed

Jenkins build is unstable: bookkeeper-release-nightly-snapshot #7

[GitHub] sijie opened a new pull request #398: Issue 397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

[GitHub] sijie commented on issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

[GitHub] sijie opened a new issue #397: [CI] publish-website job failed when mvn:release bump version to 4.6.0-SNAPSHOT

Re: [Draft] bookkeeper board report - August 2017

Re: release 4.5

Re: release 4.5

Re: Jenkins build is back to stable : bookkeeper-master #1843

release 4.5

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

Re: Jenkins build is back to stable : bookkeeper-master #1843

[GitHub] sijie commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

Re: Build failed in Jenkins: bookkeeper-postcommit-publish-website #37

Jenkins build is back to stable : bookkeeper-master #1843

Build failed in Jenkins: bookkeeper-postcommit-publish-website #37

[GitHub] merlimat commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

[GitHub] sijie commented on a change in pull request #342: Issue 338: add first draft Docker image including community suggestions

Jenkins build is still unstable: bookkeeper-master #1842

[GitHub] jiazhai closed issue #390: Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

[GitHub] jiazhai closed pull request #396: Issue 390: [CI] Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

[GitHub] zhaijack commented on issue #396: Issue 390: [CI] Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

[GitHub] sijie opened a new pull request #396: Issue 390: Test errors in TestRackawareEnsemblePlacementPolicyUsingScript

34 matches

Site Navigation

Mail list logo

Footer information