[jira] Created: (INCUBATOR-72) Clarify release policy by removing "binding" from dev vote

Clarify release policy by removing "binding" from dev vote
----------------------------------------------------------

                 Key: INCUBATOR-72
                 URL: https://issues.apache.org/jira/browse/INCUBATOR-72
             Project: Incubator
          Issue Type: Improvement
          Components: policy
            Reporter: Craig Russell
            Assignee: Craig Russell
            Priority: Minor


The policy for podling releases states

"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 Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's 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:"

This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows:

"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 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 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:"


Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/%3c9E93D575-BDDA-4505-A20E-92B69CCE335B@...%3e




--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

     [ https://issues.apache.org/jira/browse/INCUBATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Russell updated INCUBATOR-72:
-----------------------------------

    Attachment: incubator-72.patch

This patch removes the text "and only the PPMC member votes are binding".

> Clarify release policy by removing "binding" from dev vote
> ----------------------------------------------------------
>
>                 Key: INCUBATOR-72
>                 URL: https://issues.apache.org/jira/browse/INCUBATOR-72
>             Project: Incubator
>          Issue Type: Improvement
>          Components: policy
>            Reporter: Craig Russell
>            Assignee: Craig Russell
>            Priority: Minor
>         Attachments: incubator-72.patch
>
>
> The policy for podling releases states
> "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 Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's 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:"
> This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows:
> "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 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 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:"
> Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/%3c9E93D575-BDDA-4505-A20E-92B69CCE335B@...%3e

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

     [ https://issues.apache.org/jira/browse/INCUBATOR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Russell closed INCUBATOR-72.
----------------------------------

    Resolution: Fixed

svn commit -m "INCUBATOR-72 Remove reference to PPMC binding votes" site-author/incubation/Incubation_Policy.xml site-publish/incubation/Incubation_Policy.html
Sending        site-author/incubation/Incubation_Policy.xml
Sending        site-publish/incubation/Incubation_Policy.html
Transmitting file data ..
Committed revision 673789.

people.apache.org% svn up
U    incubation/Incubation_Policy.html
Updated to revision 673789.

> Clarify release policy by removing "binding" from dev vote
> ----------------------------------------------------------
>
>                 Key: INCUBATOR-72
>                 URL: https://issues.apache.org/jira/browse/INCUBATOR-72
>             Project: Incubator
>          Issue Type: Improvement
>          Components: policy
>            Reporter: Craig Russell
>            Assignee: Craig Russell
>            Priority: Minor
>         Attachments: incubator-72.patch
>
>
> The policy for podling releases states
> "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 Apache Voting Process page), and only the PPMC member votes are binding. If the majority of all votes is positive, then the Podling SHALL send a summary of that vote to the Incubator's 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:"
> This has led to confusion, and I'd like to propose that the text be changed to remove the reference to PPMC votes, as follows:
> "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 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 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:"
> Please see this email thread for additional background: http://mail-archives.apache.org/mod_mbox/incubator-general/200801.mbox/%3c9E93D575-BDDA-4505-A20E-92B69CCE335B@...%3e

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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