[incubator] branch master updated: fix up lists

[jm...@apache.org]

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

jmclean pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator.git


The following commit(s) were added to refs/heads/master by this push:
     new b52024c  fix up lists
     new a823242  Merge pull request #64 from justinmclean/master
b52024c is described below

commit b52024c459a99fb55a6b01673106e9262e1faa0b
Author: Justin Mclean <jm...@apache.org>
AuthorDate: Mon Oct 5 15:09:14 2020 +1100

    fix up lists
---
 pages/guides/distribution.ad | 17 ++++++++++++-----
 1 file changed, 12 insertions(+), 5 deletions(-)

diff --git a/pages/guides/distribution.ad b/pages/guides/distribution.ad
index 925ff8f..0a50f3e 100644
--- a/pages/guides/distribution.ad
+++ b/pages/guides/distribution.ad
@@ -25,7 +25,7 @@ Go to start of metadata
 
 Guidelines to help you comply with the ASF distribution policies
 
-One of the goals of incubation is to teach podling communities how to build and distribute ASF-compliant releases. A podling community should begin to familiarise themselves with the ASF policies for distribution. Those policies can be found at https://infra.apache.org/release-distribution. The following will help you comply with current policy.
+One of the goals of incubation is to teach podling communities how to build and distribute ASF-compliant releases. A podling community should begin to familiarise themselves with the ASF policies for distribution. Those policies can be found at link:https://infra.apache.org/release-distribution[https://infra.apache.org/release-distribution]. The following will help you comply with current policy.
 
 == Motivation
 The ASF is responsible for providing software which can be used in accordance with our license. Code or artifacts built from code without clean IP can mean that code that doesn't belong to us slips into users projects. This would expose our users and the ASF to the risk of lawsuit. One purpose of the incubating process and its release process is to ensure that our users can trust our projects. Releasing artifacts built from code that hasn't been approved by the IPMC circumvents this proc [...]
@@ -33,6 +33,7 @@ At the same time binary artifacts on distribution platforms are important to our
 
 == Release Platforms
 In addition to the Apache mirror system incubating projects may distribute artifacts on other platforms as long as they follow these general guidelines:
+
 * Releases must be placed in the Apache mirror system.
 * Source releases and convenience binaries need to be made from IPMC and PPMC approved ASF releases.
 * Where possible it should be pointed out that Apache project make source releases and convenience binaries are just a convenience for end user.
@@ -45,22 +46,26 @@ In addition to the Apache mirror system incubating projects may distribute artif
 * All PPMC members must have access to administer the platform and the credentials recorded where any PPMC member can access them.
 * Where possible these artifacts should not be referred to as releases.
 * Where possible use platforms officially supported by Infra.
+
 All of the above SHOULD be followed. The podling can ask the IPMC for permission to do otherwise.
 
 **Currently only Github, Dockerhub, and Maven are officially supported by Infra.**
 
 == Maven distribution
 To comply with ASF release and distributions please ensure the following:
+
 * The project description should include the incubator disclaimer.
 * Artifacts should be under the groupId of org.apache.<project>.
 * The official release artifacts should not contain unapproved code.
 * Release candidates, nightlys or snapshots need to be clearly marked by adding suffix in its version, like `org.apache.<project>.<component>:0.1-SNAPSHOT`
 * The POM file should set the ALv2 license as its license, Apache <project> as its developer name, and proper source control information.
-* Additional guidelines and process for releasing Maven components can be found link:https://infra.apache.org/publishing-maven-artifacts.html[on this infra page].
+
+Additional guidelines and process for releasing Maven components can be found link:https://infra.apache.org/publishing-maven-artifacts.html[on this infra page].
 
 == GitHub
 Artifacts show up on https://github.com/apache/incubator-<project>/releases.
 To comply with ASF release and distributions please ensure the following:
+
 * Any releases need to include the text of the incubation disclaimer.
 * The release page must not contain release candidates, nightly or snapshots releases that have not been tagged as prereleases. (Ignoring that GitHub also displays tags on the release page.)
 * Any releases that exist before coming into incubation need to be clearly described on the release page and tagged as such on https://github.com/apache/incubator-<project>/tags.
@@ -69,6 +74,7 @@ To comply with ASF release and distributions please ensure the following:
 == Docker
 Artifacts need to be placed in https://hub.docker.com/r/apache/<project> or https://hub.docker.com/u/apache<project>/<project>.
 To comply with ASF release and distributions please ensure the following:
+
 * The overview should include the incubator disclaimer.
 * The docker file (if it exists) should include an ASF header.
 * The docker file (if it exists) should include the incubator disclaimer.
@@ -79,6 +85,7 @@ To comply with ASF release and distributions please ensure the following:
 
 == NPM
 Artifacts show up on https://www.npmjs.com/package/apache-<project> version page.
+
 * To comply with ASF release and distributions please ensure the following:
 * The readme tab needs to include the text of the incubation disclaimer.
 * npm install apache<project> should not install an artifact containing unapproved code.
@@ -88,11 +95,11 @@ Artifacts show up on https://www.npmjs.com/package/apache-<project> version page
 
 
 == PyPI
-* Artifacts need to be placed in https://pypi.org/project/apache-<project>.
-* To comply with ASF release and distributions please ensure the following:
+Artifacts need to be placed in https://pypi.org/project/apache-<project>.
+To comply with ASF release and distributions please ensure the following:
+
 * The project description should include the incubator disclaimer.
 * pip install apache<project> should not install an artifact containing unapproved code.
 * Release candidates, nightlys or snapshots need to be clearly tagged as pre-release on https://pypi.org/project/apache-<project>/#history
 * The latest version should not point to an artifact containing unapproved code e.g. to a release candidate or snapshot
 * The meta license field should display the ALv2 license.
-


---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org