bookkeeper-distributedlog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From franckcuny <>
Subject [GitHub] incubator-distributedlog pull request #51: (WIP) DL-81: Build the distribute...
Date Tue, 13 Dec 2016 17:33:29 GMT
Github user franckcuny commented on a diff in the pull request:
    --- Diff: website/community/ ---
    @@ -0,0 +1,507 @@
    +layout: default
    +title: "DistributedLog Release Guide"
    +permalink: /community/release-guide/
    +# Apache DistributedLog Release Guide
    +* TOC
    +This page documents the procedure to make an Apache DistributedLog release. Creit to
the [Beam]( project.
We've borrow liberally from their documentation.
    +## Introduction
    +The Apache DistributedLog 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 DistributedLog 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 DistributedLog community in a public vote.
    +Each release is executed by a *Release Manager*, who is selected among the [DistributedLog
committers]({{ site.baseurl }}/community/team). 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]({{ site.baseurl }}/community/#mailing-lists).
    +Please remember that publishing software has legal consequences. This guide complements
the foundation-wide [Product Release Policy]( and [Release
Distribution Policy](
    +## Overview
    +![Alt text]({{ "/images/release-guide-1.png" | prepend: site.baseurl }} "Release Process"){:width="100%"}
    +The release process consists of several steps:
    +1. Decide to release
    +1. Prepare for the release
    --- End diff --
    use a bullet or increment the number ?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message