Page History

...

• Source releases and convenience binaries need to be made from IPMC and PPMC approved ASF releases.
• Convenience binaries need to follow licensing policy and not include any category X licensed software.
• Release candidates, nightlys and snapshots must not be advertised to the general public.
• Apache project branding and naming needs to be respected.
• It should be clear that the artifacts are under the ALv2 license.
• An incubating disclaimer must be clearly displayed where the artifacts are made available.
• 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 these artefacts should not be referred to as releases.
• Were 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.

...

At the same time binary artifacts on automated distribution platforms are important to our users for a wide variety of reasons. This document is intended to balance these priorities. If you believe you have a case in which this document is inadequate to your situation please bring this to our attention by mailing either general@incubator.apache.org or private@incubator.apache.org

...

• The project description should include the incubator disclaimer.
• The project description should also include `All Apache <project> releases are in the form of source code, binary/bytecode packages are produced as a convenience to users.` and the URL address of the Apache Release.
• Artifact 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.

...

• The readme tab needs to include the text of the incubation disclaimer.
• npm install apache<project> should not install an artifact containing unapproved code.
• The latest release should not point to an artifact containing unapproved code e.g. a release candidate or snapshot.
• Release candidates, nightlys or snapshots need to be clearly tagged.
• The license field should display the ALv2 license.

PiPy

Artifacts Artefacts need to be placed in https://pypi.org/project/apache<project>/

To comply with ASF release and distributions please ensure the following:

...