incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [incubator] paulk-asert commented on a change in pull request #21: Update, simplify and modernise policy
Date Sat, 27 Jul 2019 23:50:54 GMT
paulk-asert commented on a change in pull request #21: Update, simplify and modernise policy
URL: https://github.com/apache/incubator/pull/21#discussion_r307980815
 
 

 ##########
 File path: pages/policy/incubation.ad
 ##########
 @@ -72,25 +78,27 @@ project has yet to be fully endorsed by the ASF.
 ____
 
 Podlings wishing to use a different disclaimer message MUST have the
-disclaimer approved by the Incubator PMC prior to use.
+disclaimer approved by the Incubator PMC before use.
 
 For releases, the text SHOULD be included in a separate DISCLAIMER file
 stored alongside the NOTICE and LICENSE files.
 
 === Releases
 
-See the guidelines for link:/guides/releasemanagement.html[Podling releases] in conjunction
with this policy. Podlings are not yet fully accepted as part of the Apache Software Foundation.
No release made by a Podling will be endorsed by the ASF.  Unendorsed releases may be made
by Podlings subject to the following policy. Podlings in Incubation SHALL NOT perform any
releases of software without the explicit approval of the Incubator PMC. Such approval SHALL
be given only after the Incubator PMC has followed the process detailed in these guidelines,
and SHALL NOT occur until all source has been legally transferred to the ASF. Therefore, should
a Podling decide it wishes to perform a release, the Podling SHALL hold a vote on the Podling's
public dev list. At least three +1 votes are required (see the http://www.apache.org/foundation/voting.html[Apache
Voting Process] page). If the majority of all votes is positive, then the Podling SHALL send
a summary of that vote to the Incubator's link:/howtoparticipate.html#Mailing+lists[general]
list and formally request the Incubator PMC approve such a release. Three +1 Incubator PMC
votes are required. Below is an example showing how an incubating project managed this process:
+See the guidelines for link:/guides/releasemanagement.html[Podling releases] for good practices
on making releases.
+
+Podlings are not fully accepted as part of the Apache Software Foundation. Podlings MUST
NOT perform any releases of software without the approval of the Incubator PMC. When a Podling
decide it wants to make an release, the Podling MUST hold a vote on their public dev list.
At least three +1 votes are required (see the http://www.apache.org/foundation/voting.html[Apache
Voting Process] page) and more +1 votes than -1 votes. If the vote passes the Podling MUST
send a summary of that vote to the Incubator's link:/howtoparticipate.html#Mailing+lists[general]
list and request that the Incubator PMC approve the release. Three +1 Incubator PMC votes
are required to approve a release. Below is an example showing how an incubating project managed
this process:
 
-- link:++http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43C1C0A0.7040401@roguewave.com%3e++[Post
to the Podling dev list calling the vote.]
-- link:++http://mail-archives.apache.org/mod_mbox/incubator-general/200601.mbox/%3c43D7AC9E.30205@roguewave.com%3e++[Post
to the Incubator's general list requesting approval from the Incubator PMC.]
+- link:++https://lists.apache.org/thread.html/7e9c475d07c0e12f813226aa123f54969ebb21a2277b32e9bd366d96@%3Cdev.plc4x.apache.org%3E++[Post
to the Podling dev list calling the vote.]
+- link:++https://lists.apache.org/thread.html/06655226ba08c16a8cb273f9b45e0b0a15ebaed0d06783fdd06a03f6@%3Cgeneral.incubator.apache.org%3E++[Post
to the Incubator's general list requesting approval from the Incubator PMC.]
 
-Should the Incubator PMC, in accordance with these guidelines vote to approve the request,
the Podling MAY perform the release under the following constraints:
+Should the Incubator PMC vote to approve a release, the Podling MAY make that release available
to the public, only if:
 
-- the release archive MUST contain the word "incubating" in the filename; and
-- the release archive MUST contain an Incubation disclaimer (as described in the previous
section), which SHOULD be placed in a DISCLAIMER file.
+- The release archive(s) MUST include the word "incubating" in the filename.
+- The release archive(s) MUST contain a disclaimer (see above), which SHOULD be placed in
a DISCLAIMER file.
 
-Releases for *podling* MUST be distributed through *++http://www.apache.org/dist/incubator/++_podling_*
In addition, the Podling MAY choose to distribute approved releases through other channels
like the central Maven repository.
+Releases for *Podling* MUST be distributed through *++http://www.apache.org/dist/incubator/++_Podling_*
Also the Podling MAY choose to distribute approved releases through other channels like the
central Maven repository.
 
 Review comment:
   s/Releases for Podling/Releases for **the** Podling/

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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


Mime
View raw message