(Anybody knows what's the deal with all the .invalid e-mail addresses?) Anyway. ASF has voting rules, and some things like releases follow specific rules: https://www.apache.org/foundation/voting.html#ReleaseVotes
So, for releases, ultimately, the only votes that "count" towards the final tally are PMC votes. But everyone is welcome to vote, especially if they have a reason to -1 a release. PMC members can use that to guide how they vote, or the RM can use that to drop the RC unilaterally if he agrees with the reason. On Thu, Mar 28, 2019 at 3:47 PM Jonatan Jäderberg <jonatan.jaderb...@neo4j.com.invalid> wrote: > > +1 (user vote) > > btw what to call a vote that is not pmc or committer? > Some people use "non-binding”, but nobody says “my vote is binding”, and if > some vote is important to me, I still need to look up the who’s-who of the > project to be able to tally the votes. > I like `user vote` for someone who has their say but is not speaking with any > authority (i.e., not pmc/committer). wdyt? > > Also, let’s get this release out the door! > > cheers, > Jonatan > > On 28 Mar 2019, at 21:31, DB Tsai <dbt...@dbtsai.com.INVALID> wrote: > > +1 from myself > > On Thu, Mar 28, 2019 at 3:14 AM Mihaly Toth <mt...@cloudera.com.invalid> > wrote: >> >> +1 (non-binding) >> >> Thanks, Misi >> >> Sean Owen <sro...@apache.org> ezt írta (időpont: 2019. márc. 28., Cs, 0:19): >>> >>> +1 from me - same as last time. >>> >>> On Wed, Mar 27, 2019 at 1:31 PM DB Tsai <d_t...@apple.com.invalid> wrote: >>> > >>> > Please vote on releasing the following candidate as Apache Spark version >>> > 2.4.1. >>> > >>> > The vote is open until March 30 PST and passes if a majority +1 PMC votes >>> > are cast, with >>> > a minimum of 3 +1 votes. >>> > >>> > [ ] +1 Release this package as Apache Spark 2.4.1 >>> > [ ] -1 Do not release this package because ... >>> > >>> > To learn more about Apache Spark, please see http://spark.apache.org/ >>> > >>> > The tag to be voted on is v2.4.1-rc9 (commit >>> > 58301018003931454e93d8a309c7149cf84c279e): >>> > https://github.com/apache/spark/tree/v2.4.1-rc9 >>> > >>> > The release files, including signatures, digests, etc. can be found at: >>> > https://dist.apache.org/repos/dist/dev/spark/v2.4.1-rc9-bin/ >>> > >>> > Signatures used for Spark RCs can be found in this file: >>> > https://dist.apache.org/repos/dist/dev/spark/KEYS >>> > >>> > The staging repository for this release can be found at: >>> > https://repository.apache.org/content/repositories/orgapachespark-1319/ >>> > >>> > The documentation corresponding to this release can be found at: >>> > https://dist.apache.org/repos/dist/dev/spark/v2.4.1-rc9-docs/ >>> > >>> > The list of bug fixes going into 2.4.1 can be found at the following URL: >>> > https://issues.apache.org/jira/projects/SPARK/versions/2.4.1 >>> > >>> > FAQ >>> > >>> > ========================= >>> > How can I help test this release? >>> > ========================= >>> > >>> > If you are a Spark user, you can help us test this release by taking >>> > an existing Spark workload and running on this release candidate, then >>> > reporting any regressions. >>> > >>> > If you're working in PySpark you can set up a virtual env and install >>> > the current RC and see if anything important breaks, in the Java/Scala >>> > you can add the staging repository to your projects resolvers and test >>> > with the RC (make sure to clean up the artifact cache before/after so >>> > you don't end up building with a out of date RC going forward). >>> > >>> > =========================================== >>> > What should happen to JIRA tickets still targeting 2.4.1? >>> > =========================================== >>> > >>> > The current list of open tickets targeted at 2.4.1 can be found at: >>> > https://issues.apache.org/jira/projects/SPARK and search for "Target >>> > Version/s" = 2.4.1 >>> > >>> > Committers should look at those and triage. Extremely important bug >>> > fixes, documentation, and API tweaks that impact compatibility should >>> > be worked on immediately. Everything else please retarget to an >>> > appropriate release. >>> > >>> > ================== >>> > But my bug isn't fixed? >>> > ================== >>> > >>> > In order to make timely releases, we will typically not hold the >>> > release unless the bug in question is a regression from the previous >>> > release. That being said, if there is something which is a regression >>> > that has not been correctly targeted please ping me or a committer to >>> > help target the issue. >>> > >>> > >>> > DB Tsai | Siri Open Source Technologies [not a contribution] | >>> > Apple, Inc >>> > >>> > >>> > --------------------------------------------------------------------- >>> > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>> > -- > - DB Sent from my iPhone > > -- Marcelo --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
