Hi Craig,
Thanks for your proposed update which would helps all the incubator release managers make release procedure smoothly. BTW, > All votes cast during the dev vote are carried over to the incubator general > vote. In particular, IPMC Member votes including Mentor votes cast in the dev > vote are binding in the general vote. And votes can be changed during the > general vote; the last vote cast by any voter is considered definitive. How about votes from PPMCs in dev@? As votes from PPMCs are unbinding in general@, release manages would ignore those votes from dev@, and do not present their names and votes when summarizing? Or on the contrary? Thank your help for a novice in advance. Juan Pan panj...@apache.org Juan Pan(Trista), Apache ShardingSphere On 11/23/2019 04:47，Craig Russell<apache....@gmail.com> wrote： I believe that the current cookbook recommendations need an update. [1] 1. "Binding" should always refer to IPMC members' votes. This is a source of confusion for many podling communities. 2. Votes on the dev list should automatically carry over to the general list. Assuming that there is no change to the artifacts, the only reason for the dev vote not to carry over is that the voter changed their mind, which is an exception that should be documented in the general thread. 3. All votes count. All input is valuable. All votes whether on dev or incubator general should be tallied. 4. The discussion needs to include the recent DISCLAIMER-WIP changes to release protocol. Here is my proposed update: Podling Releases A podling is expected to make several software releases during incubation, that progress toward being fully conformant with the ASF Release Policy http://www.apache.org/legal/release-policy.html . A fully conformant release is expected as a condition of graduation. Podling releases must include the word "incubating" in any release file names and must include a DISCLAIMER or DISCLAIMER-WIP https://incubator.apache.org/guides/releasemanagement.html#choice_of_disclaimers to avoid any confusion as to the project’s status. As podlings are not yet "real" ASF projects, it is important to set expectations right. Also, voting on podling releases happens in two phases: First, the podling votes on the release on their dev mailing list. The main goal of this vote is for the podling community to practice and learn voting on releases. The vote is successful if there are at least three +1 votes from PPMC members, and more +1 votes from PPMC members than -1 votes from PPMC members. Then, if that first vote is successful, an Incubator PMC vote is held on the incubator general mailing list. This is required to make the vote an Act of the Foundation, as is required for all ASF releases. When the release manager calls for a vote on the general list, the results of the dev list vote are summarized in the vote message. All votes cast during the dev vote are carried over to the incubator general vote. In particular, IPMC Member votes including Mentor votes cast in the dev vote are binding in the general vote. And votes can be changed during the general vote; the last vote cast by any voter is considered definitive. At the conclusion of the vote, the results are announced to the general incubator list. All votes from the dev list and general list are reported, including the names and roles of the voters. The vote is successful if there are at least three +1 votes from IPMC members, and more +1 votes from IPMC members than -1 votes from IPMC members. Craig Current incubator web page: [1] Podling Releases https://incubator.apache.org/cookbook/#podling_releases A podling is expected to make several software releases during incubation, that gradually progress towards being fully conformant to the ASF Release Policy. In addition to following that policy, podling releases must include the word "incubating" in any release file names and a DISCLAIMER (TODO: link) to avoid any confusion as to the project’s status. As podlings are not "real" ASF projects yet, it is important to set expectations right. Also, voting on podling releases happens in two phases: First, the podling votes on the release on their dev mailing list, with PPMC members votes being "binding" and others being welcome to cast consultative votes. The main goal of this vote is for the podling community to practice and learn voting on releases. Then, if that first vote is successful, an Incubator PMC vote is held on the Incubator general mailing list. This is required to make the vote an Act of the Foundation, as is required for all ASF releases. Incubation mentors can optionally indicate that their votes in the first phase can be carried on to the Incubator PMC vote. If three mentors have voted this means the "three +1 votes" requirement is already fulfilled when that second vote starts, which can speed up things. Craig L Russell c...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
