Page History

...

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

Maven distribution

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

• 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.

GitHub

Artifacts show up on https://github.com/apache/incubator-<project>/releases

...

• 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.

Maven distribution

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

• 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.