www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mar...@apache.org
Subject svn commit: r1722397 - /infrastructure/site/trunk/content/legal/release-policy.mdtext
Date Wed, 30 Dec 2015 19:12:52 GMT
Author: marvin
Date: Wed Dec 30 19:12:52 2015
New Revision: 1722397

URL: http://svn.apache.org/viewvc?rev=1722397&view=rev
Log:
Move items in _Release FAQ_ down one h-level.

Move all sections which are part of the _Release FAQ_ down one h-level,
so that they all fall under the _Release FAQ_ hierarchy and the page
divides cleanly into two sections: _Release Policy_ and _Release FAQ_.

Modified:
    infrastructure/site/trunk/content/legal/release-policy.mdtext

Modified: infrastructure/site/trunk/content/legal/release-policy.mdtext
URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/legal/release-policy.mdtext?rev=1722397&r1=1722396&r2=1722397&view=diff
==============================================================================
--- infrastructure/site/trunk/content/legal/release-policy.mdtext (original)
+++ infrastructure/site/trunk/content/legal/release-policy.mdtext Wed Dec 30 19:12:52 2015
@@ -181,7 +181,7 @@ Formalize additional official policies a
 
 # Release FAQ # {#releases}
 
-## Why Do We Need a Foundation-Wide Policy? ## {#why}
+### Why Do We Need a Foundation-Wide Policy? ### {#why}
 
 In the traditional open source development methodology practiced
 at volunteer liability-limiting organizations like Apache, it is necessary to draw
@@ -210,7 +210,7 @@ we prefer robust, reviewable decision-ma
 are thinking of proposing an alternative process for the board to consider, be sure
 your targets reflect this.
 
-## What Is A Release? ## {#what}
+### What Is A Release? ### {#what}
 
 Releases are, by definition, anything that is published beyond the group
 that owns it. In our case, that means any publication outside the group of
@@ -242,7 +242,7 @@ binary/bytecode package must have the sa
 release and may only add binary/bytecode files that are the result of
 compiling that version of the source code release.
 
-## How Do The Types Of Apache Software Distribution Differ? ## {#release-types}
+### How Do The Types Of Apache Software Distribution Differ? ### {#release-types}
 
 - **Test Packages** are not Apache releases. All releases require due
 process and official approval. Test packages are for testing ongoing
@@ -273,9 +273,9 @@ features or functionality, are usually r
 Releases that only represent a project milestone and are intended only for
 bleeding-edge developers working outside the project are called "alpha".
 
-# Release Management Questions # {#management}
+## Release Management Questions ## {#management}
 
-## Where do releases go? ##
+### Where do releases go? ###
 
 A release isn't 'released' until the contents are in the project's 
 distribution directory, which is a subdirectory of `www.apache.org/dist/`.
@@ -285,7 +285,7 @@ releases on `repository.apache.org` besi
 The distribution directory is required, 
 while the repository system is an optional convenience.
 
-## What Must Every ASF Release Contain? ## {#what-must-every-release-contain}
+### What Must Every ASF Release Contain? ### {#what-must-every-release-contain}
 
 Every ASF release **must** contain a source package, which must be
 sufficient for a user to build and test the release provided they have
@@ -312,7 +312,7 @@ contain only [appropriately](/legal/reso
 in the [foundation website](/) and in the [release
 licensing FAQ](#license).
 
-## What are the ASF requirements on approving a release? ## {#approving-a-release}
+### What are the ASF requirements on approving a release? ### {#approving-a-release}
 
 Votes on whether a package is ready to be released use 
 [majority approval](http://www.apache.org/foundation/glossary.html#MajorityApproval) -- 
@@ -323,7 +323,7 @@ to download the signed source code packa
 resulting executable on their own platform, along with also verifying that the 
 package meets the requirements of the ASF policy on releases.
 
-## How Should Releases Be Announced? ## {#release-announcements}
+### How Should Releases Be Announced? ### {#release-announcements}
 
 Please ensure that you wait at least 24 hours after uploading a new release
 before updating the project download page and sending the announcement email(s).
@@ -351,7 +351,7 @@ uploaded to famous pgp sites (e.g. http:
 either be the one used to sign the release or one that is cross-signed by
 that key.
 
-## Is There A Guide To Best Practice? ## {#best-practice}
+### Is There A Guide To Best Practice? ### {#best-practice}
 
 See the Incubator [release management
 guide (draft)](http://incubator.apache.org/guides/releasemanagement.html#best-practice).
@@ -360,7 +360,7 @@ established Apache project.  (The author
 [this one](http://subversion.apache.org/docs/community-guide/releasing#release-creating),
 from his project.)
 
-## Must releases be built on hardware owned and controlled by the committer? ## {#owned-controlled-hardware}
+### Must releases be built on hardware owned and controlled by the committer?  ### {#owned-controlled-hardware}
 
 Strictly speaking, releases must be **[verified](https://svn.apache.org/repos/private/committers/tools/releases/compare_dirs.pl)**
 on hardware owned and controlled by the committer.  That means hardware the 
@@ -378,9 +378,9 @@ files (especially binary files) is not f
 from a source control tag.  It does not refer to testing that artifact for
 technical quality.*
 
-# Release Distribution and Mirroring Questions # {#mirroring}
+## Release Distribution and Mirroring Questions ## {#mirroring}
 
-## Where can we host test packages (nightly builds and release candidates)? ## {#host-rc}
+### Where can we host test packages (nightly builds and release candidates)?  ### {#host-rc}
 
 Test packages are for use by consenting developers and interested community
 members only, so they should not be hosted or linked on pages intended for end
@@ -393,7 +393,7 @@ or the staging features of repository.ap
 to host release candidates posted for developer testing/voting (prior to being,
 potentially, formally blessed as a GA release).
 
-## Where can we host public (GA) releases? ## {#host-GA}
+### Where can we host public (GA) releases? ### {#host-GA}
 
 Current releases must be served from the ASF mirroring system by placing them under
 `http://www.apache.org/dist/`.  (How to upload releases to the `dist/`
@@ -411,7 +411,7 @@ and source control repositories (`svn.ap
 may not be used to distribute releases --- that is, releases should not be
 downloaded from them.
 
-## How are releases archived? ## {#archived}
+### How are releases archived? ### {#archived}
 
 All releases must be archived on <http://archive.apache.org/dist/>.
 
@@ -425,7 +425,7 @@ from `http://www.apache.org/dist/`.
 If you have (legacy?) releases that never got archived, 
 ask infra to copy them to `http://archive.apache.org/dist/`.
 
-## When Should An Old Release Be Archived? ## {#when-to-archive}
+### When Should An Old Release Be Archived? ### {#when-to-archive}
 
 `/www.apache.org/dist` should contain *the latest release in each branch 
 that is currently under development*. When development ceases on a version 
@@ -443,7 +443,7 @@ see [How Is An Old Release Moved To The
 If Apache Foo 1.2 is a new branch, and development continues on 1.1 in 
 parallel, then it is acceptable to serve both 1.1.a and 1.2.x from `/dist`.
 
-## How do I upload a release ? {#upload-ci}
+### How do I upload a release ? ### {#upload-ci}
 
 By committing your release tarballs to the appropriate subdirectory (i.e. TLP name) of the
 [`https://dist.apache.org/repos/dist/release/`](https://dist.apache.org/repos/dist/release/)
@@ -462,7 +462,7 @@ If the Release Manager is not a member o
 The PMC can also vote to let non-PMC-members update the dist/release area.
 To get this set up, please open a JIRA ticket at the [INFRA JIRA](https://issues.apache.org/jira/browse/INFRA)
referencing the PMC vote.
 
-## Where can I stage a release candidate? {#stage}
+### Where can I stage a release candidate? ### {#stage}
 
 There is also a development area under
 `https://dist.apache.org/repos/dist/dev/<TLP name>/`
@@ -479,7 +479,7 @@ in order to publish them.
 
 Commit mails to the `dist/` repository go to your normal project mailing lists.
 
-## Do I need to talk to Infrastructure before distributing a release? {#heads-up}
+### Do I need to talk to Infrastructure before distributing a release? ### {#heads-up}
 
 Most projects can just distribute a release as described in the previous two
 questions.  However, releases that are likely to strain the mirroring and
@@ -491,7 +491,7 @@ advance.
 Specific exemptions from other dist policies (such as what may or must or must
 not be distributed via the mirrors) also need to be coordinated with Infrastructure.
 
-## Which Directory For What Build? ## {#build-directories}
+### Which Directory For What Build? ### {#build-directories}
 
 | Type             | Location                 |
 |------------------|--------------------------|
@@ -499,29 +499,29 @@ not be distributed via the mirrors) also
 | Current Releases | www.apache.org/dist      |
 | Older Releases   | archive.apache.org/dist  | 
 
-## How Is An Old Release Moved To The Archives? ## {#how-to-archive}
+### How Is An Old Release Moved To The Archives? ### {#how-to-archive}
 
 `/www.apache.org/dist` is automatically archived. Therefore, a copy of an
 official release will already exist in the archives. To move a release to
 the archives, just delete the copy in `/www.apache.org/dist`. Remember to
 update any links from the download page.
 
-## How do I release Maven Artifacts? ## {#maven-artifacts}
+### How do I release Maven Artifacts? ### {#maven-artifacts}
 
 See the [Publishing Maven
 Releases](http://www.apache.org/dev/publishing-maven-artifacts.html) guide.
 
-# Release Licensing Questions # {#license}
+## Release Licensing Questions ## {#license}
 
 Please read [Applying the Apache License, Version
 2.0](apply-license) and check the [Apache Licenses](/licenses/) and 
 [Apache Legal](/legal/) pages for current information.
 
-## Which Files Must Contain An ASF License Text? ## {#which-files-contain-license}
+### Which Files Must Contain An ASF License Text? ### {#which-files-contain-license}
 
 Every source file must contain the appropriate ASF License text.
 
-## Is A Full Copy Of The License Required In Each Source File? ## {#full-copy-for-each-source-file}
+### Is A Full Copy Of The License Required In Each Source File? ### {#full-copy-for-each-source-file}
 
 In short, only one copy of the license is needed per distribution. This
 full license file should be placed at the root of the distribution in a
@@ -529,7 +529,7 @@ file named LICENSE. For software develop
 need only contain the [boilerplate
 notice](http://www.apache.org/legal/src-headers.html#headers).
 
-## Where Is The Right Place For Attribution Notices? ## {#attribution-notices}
+### Where Is The Right Place For Attribution Notices? ### {#attribution-notices}
 
 The new license allows for a NOTICE file that contains such attribution
 notices (including the Apache attribution notice). Read
@@ -542,14 +542,14 @@ next to the LICENSE file.
 Ensure that the standard ASF attribution notice is contained in any new
 NOTICE file created.
 
-## What Content Is Appropriate For The NOTICE File? ## {#notice-content}
+### What Content Is Appropriate For The NOTICE File? ### {#notice-content}
 
 Read [this](http://apache.org/legal/src-headers.html#notice).
 
 Only mandatory information required by the product's software licenses. Not
 suitable for normal documentation.
 
-## Is A NOTICE File Required For Pure ASF Code? ## {#notice-required}
+### Is A NOTICE File Required For Pure ASF Code? ### {#notice-required}
 
 Yes! The NOTICE file must contain the standard ASF attribution, given
 below:
@@ -564,7 +564,7 @@ The official wording was established in
 
 <!-- Note: the text was originally added in: r201713 see #INFRA-367 -->
 
-## If An Artifact Contains Code Under Several Licenses, Should It Contain Several License
Files? ## {#distributing-code-under-several-licenses}
+### If An Artifact Contains Code Under Several Licenses, Should It Contain Several License
Files? ### {#distributing-code-under-several-licenses}
 
 When an artifact contains code under several licenses, the LICENSE file
 should contain details of all these licenses. For each component which is
@@ -575,7 +575,7 @@ artifact with a pointer to it from the L
 [Here](https://svn.apache.org/repos/asf/httpd/httpd/trunk/LICENSE) is an
 example showing appended licences.
 
-## What Are The Requirements To Distribute Other Artifacts In Addition To The Source Package?
## {#distribute-other-artifacts}
+### What Are The Requirements To Distribute Other Artifacts In Addition To The Source Package?
### {#distribute-other-artifacts}
 
 ASF releases typically contain additional material together with the source
 package. This material may include documentation concerning the release but
@@ -593,9 +593,9 @@ Nothing in this section is meant to supe
 [here](#what) and [here](#what-must-every-release-contain) that all
 releases be primarily based on a signed source package.
 
-# Questions About Release Statistics # {#stats}
+## Questions About Release Statistics ## {#stats}
 
-## Is There Any Way To Measure How Many Times XYZ Has Been Downloaded? ## {#downloads}
+### Is There Any Way To Measure How Many Times XYZ Has Been Downloaded? ### {#downloads}
 
 Not directly. Files are downloaded from the mirrors. Apache does not
 require mirrors to collect statistics about downloads.



---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message