This policy governs how Apache Top Level Projects (TLPs) distribute releases of their software through the technical channels that Infra maintains, and through other distribution platforms. It complements the formal Apache Release Policy, which defines what must be in a software release; and the Release Creation Process page, which describes the steps for a PMC to create a release.
Note: RFC 2119 describes how to interpret must, should, should not and similar terms.
downloads.apache.org/. This directory provides access for current releases to the ASF content distribution network (CDN), through which most users download releases.
Every top-level project at Apache has its own public distribution directory, which is a subdirectory of
downloads.apache.org/. Each PMC is responsible for all artifacts within their project's distribution directory.
Apache Incubator podlings cannot create official ASF releases; see the Incubator documentation for details and discussion.
The Apache Release Policy governs the content of official Apache releases and the process by which projects create valid releases.
The Policy specifies that TLPs may distribute binary packages, provided by the project or third parties which meet certain criteria, may be distributed alongside official source packages. Such packages are sometimes referred to as "convenience binaries" or "PMC-approved artifacts", to distinguish them from other binary packages.
Projects must upload all official releases to the official distribution channel,
downloads.apache.org/. Content suitable for the official distribution channel includes:
If an Apache PMC wishes to publish additional materials through the official distribution channel and there is any question about the suitability of the materials, the PMC must consult with the ASF Board before publishing.
Unreleased materials, in original or derived form,
Projects must coordinate with Infra in advance about releases larger than 1GB of artifacts to mitigate strain on content distribution resources.
See the release signing page.
For every artifact distributed to the public through Apache channels, the PMC
For new releases, PMCs must supply SHA-256 and/or SHA-512 and should not supply MD5 or SHA-1. You do not need to change existing releases.
You must form the names of individual signature and checksum files by adding to the name of the artifact the appropriate suffix:
.ascfor a (ASCII-armored) PGP signature
.sha256for an SHA-256 checksum
.sha512for an SHA-512 checksum
Noted for completeness that this specification also applies to deprecated file types:
.md5for an MD5 checksum
.sha1for an SHA-1 checksum
Regarding signature and checksum files:
.shashould not be be used and
.shafiles should not be provided.
.sigfiles must not be provided.
.mdsfiles (containing multiple checksums) may be provided for individual files as long as the included checksums comply with the above requirements.
Regarding KEYS files:
https://[www.]apache.org/dist/...still work, but new links should use
archive.apache.org, and you may also link to them.
archive.apache.org. This automated process generally adds releases to the archive about a day after they first appear on
Infra operates an Apache Maven repository manager at
repository.apache.org. Projects may use the repository system as a downstream channel to redistribute released materials via Maven Central, and may use it to distribute snapshots containing unreleased materials directly to consenting members of a project development community.
Projects must not point or refer to
repository.apache.org directly in download pages, release announcements or emails. Instead, any public download links for those releases should point to Maven Central.
Read more about Maven releases for Apache projects.
The ASF manages a number of distribution platforms that projects are welcome to use. Projects can distribute PMC-approved artifacts on ASF managed distribution platforms and other distribution platforms as long as those binaries comply with ASF release, licensing, branding and trademark policies. Currently, ASF managed platforms include GitHub and Docker.
The ASF only supports two modes of operation on Docker Hub: automated builds based on tags, and some more generalized access (see notes in the Jira ticket INFRA-14586.) Note that Docker Hub is not an approved release channel for ASF artifacts. Anything you do on Docker Hub requires the description and supporting documentation to be clear that these are convenience releases, not official distribution artifacts.
See the Docker Hub policy for further information.
This policy is required for all Apache projects. The V.P. of Apache Infrastructure must approve changes to this policy.