Exactly.  Not enough binding/qualified votes to approve the release.
Thanks for confirming!  And, getting the project [ well, those that read
the dev list ], on the same page.



On Tue, May 10, 2022 at 2:10 PM Joshua Poore <poor...@apache.org> wrote:

> Austin,
>
> Because we’re still a podling, PPMC (Podling Project Management Committee)
> VOTEs don’t count toward releases RE Apache release guideline. Think of
> Podlings as smaller projects under the larger “Incubator” project. We need
> +3 IPMC (Incubator Podline Management Committee) VOTES to pass release
> VOTES (and more +1 and -1). That doesn’t mean that “community” VOTEs —
> PPMC, Committer, and anyone on Dev—don’t count for anything. Still
> appreciated at the IPMC level.
>
> As it stands we have +1 Binding VOTEs toward release and will need to
> rally at the IPMC level. Furkan and our mentors are all IPMC.
>
> Apologies for the delay in the release VOTE. I should have delegated
> earlier in light of havoc at home.
>
> > On May 7, 2022, at 10:11 PM, Austin Bennett <whatwouldausti...@gmail.com>
> wrote:
> >
> > Furkan,
> >
> > Trying to understand the process, esp. understand PPMC, IPMC, and mentor
> > distinction.  I see you as a mentor [1], and look like for someone to be
> a
> > mentor, they must be  IPMC which you are [2] .
> >
> > These comments are to understand ASF Process, and to ensure there are
> docs
> > ( perhaps I'm failing to find, as I've only done a cursory search thus
> far
> > ).
> >
> > According to [3] "The only time when a PPMC member’s vote is binding is
> for
> > the addition of new PPMC members and committers. Release votes are only
> > binding for IPMC members." ... so that seems like for a release the only
> > binding vote cast has been @Furkam.  As I see it [2], Gedd Johnson and
> > Joshua Poore are committers ( not PMC ) of the incubator, so wouldn't
> cast
> > binding votes?
> >
> > Though, that also seems strange.  So, can you help me understand the
> > process?  As I am likely missing some docs/info somewhere?  Or, perhaps
> I'm
> > misunderstanding the acronyms.
> >
> > Thanks!
> > Austin
> >
> >
> >
> > [1]  https://incubator.apache.org/projects/flagon.html
> >
> > [2] http://home.apache.org/phonebook.html?pmc=incubator
> >
> > [3] https://incubator.apache.org/guides/ppmc.html#ppmc_and_binding_votes
> >
> >
> >
> > On Sat, May 7, 2022 at 5:26 PM Furkan KAMACI <furkankam...@gmail.com>
> wrote:
> >
> >> Hi,
> >>
> >> We have 3 binding votes (Joshua Poore, Gedd Johnson, Furkan KAMACI) and
> 1
> >> non-binding vote (Austin Bennett).
> >>
> >> So, the vote has passed in terms of the ASF rules.
> >>
> >> Kind Regards,
> >> Furkan KAMACI
> >>
> >> On Sun, May 8, 2022 at 3:21 AM Austin Bennett <
> whatwouldausti...@gmail.com
> >>>
> >> wrote:
> >>
> >>> At least 72 hours have passed :-)
> >>>
> >>> But ...  doesn't look like received 3 +1 votes from PPMC; was there
> >> enough
> >>> for this to pass?  I can look up but don't recall off head the
> incubating
> >>> project guidelines.
> >>>
> >>>
> >>>
> >>>
> >>> On Sat, May 7, 2022 at 3:52 PM Furkan KAMACI <furkankam...@gmail.com>
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>> Is this voting closed or not?
> >>>>
> >>>> Kind Regards,
> >>>> Furkan KAMACI
> >>>>
> >>>> On Tue, May 3, 2022 at 10:04 PM Austin Bennett <
> >>>> whatwouldausti...@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Based on what has been checked, it looks good to me, so +1 (
> >>> non-binding
> >>>>> ).
> >>>>>
> >>>>> A process questions to ensure things get covered, long term:
> >>>>>
> >>>>> * is there a concrete list for things actually desired to be checked
> >> as
> >>>>> part of release process ( I see some things, ex:
> >>>>> https://github.com/apache/incubator-flagon/tree/master/release and
> >>> some
> >>>>> info https://flagon.incubator.apache.org/releases/ and
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
> >>>>> but not an actual list of things we want to ensure are covered by a
> >>>> machine
> >>>>> or human )?
> >>>>>
> >>>>> Also, I don't recall -- Does the project have a targeted release
> >> cycle
> >>> (
> >>>>> ex: every month, quarter, etc ), or just cutting releases as desired?
> >>>> That
> >>>>> might help inform what all checks are worth automating.
> >>>>>
> >>>>>
> >>>>> On Tue, May 3, 2022 at 11:43 AM Joshua Poore <poor...@me.com.invalid
> >>>
> >>>>> wrote:
> >>>>>
> >>>>>> Bump!
> >>>>>>
> >>>>>>> On Apr 23, 2022, at 1:32 PM, Joshua Poore <poor...@me.com.INVALID
> >>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> Reminder! Please VOTE for this release!!
> >>>>>>>
> >>>>>>> Joshua Poore
> >>>>>>>
> >>>>>>>
> >>>>>>>> On Apr 13, 2022, at 5:16 PM, Furkan KAMACI <
> >>> furkankam...@gmail.com>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> +1 from me.
> >>>>>>>>
> >>>>>>>> I checked:
> >>>>>>>>
> >>>>>>>> - Incubating in name
> >>>>>>>> - DISCLAIMER exists
> >>>>>>>> - LICENSE and NOTICE are fine
> >>>>>>>> - No unexpected binary files
> >>>>>>>> - Checked PGP signatures
> >>>>>>>> - Checked checksums
> >>>>>>>> - Code compiles and tests successfully run
> >>>>>>>>
> >>>>>>>> Kind Regards,
> >>>>>>>> Furkan KAMACI
> >>>>>>>>
> >>>>>>>>> On Wed, Apr 13, 2022 at 11:54 PM Joshua Poore <
> >>> poor...@apache.org>
> >>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> REMINDER PPMC, Mentors—please don’t forget to VOTE for this
> >>>> release!!
> >>>>>>>>>
> >>>>>>>>> This release contains some great PR work from our community!!!
> >>>>>>>>>
> >>>>>>>>>>> On Apr 11, 2022, at 12:05 PM, Gedd Johnson <
> >>> uncleg...@apache.org
> >>>>>
> >>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> [x] +1, let's get it released!!!
> >>>>>>>>>>
> >>>>>>>>>> [x ] Build and Unit Tests Pass
> >>>>>>>>>> [x ] Integration Tests Pass
> >>>>>>>>>> [x ] "Incubating" in References to Project and Distribution
> >> File
> >>>>> Names
> >>>>>>>>>> [x ] Signatures and Hashes Match Keys
> >>>>>>>>>> [x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and
> >> Binary
> >>>>>> Release
> >>>>>>>>>> Packages
> >>>>>>>>>> [x ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF
> >> and
> >>>>>>>>> Incubator
> >>>>>>>>>> Policy
> >>>>>>>>>> [x ] CHANGELOG included with release distribution
> >>>>>>>>>> [x ] All Source Files Have Correct ASF Headers
> >>>>>>>>>> [x ] No Binary Files in Source Release Packages
> >>>>>>>>>>
> >>>>>>>>>> - Gedd Johnson
> >>>>>>>>>>
> >>>>>>>>>> On Sun, Apr 10, 2022 at 12:38 PM Joshua Poore <
> >>> poor...@apache.org
> >>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> +1 (PPMC)
> >>>>>>>>>>>
> >>>>>>>>>>> I checked:
> >>>>>>>>>>>
> >>>>>>>>>>> [ x ] Build and Unit Tests Pass
> >>>>>>>>>>> [ x ] Integration Tests Pass (Example Page, Webpack (NPM),
> >>> React
> >>>>>> (NPM)
> >>>>>>>>>>> [ x ] "Incubating" in References to Project and Distribution
> >>> File
> >>>>>> Names
> >>>>>>>>>>> [ x ] Signatures and Hashes Match Keys
> >>>>>>>>>>> [ x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and
> >>> Binary
> >>>>>> Release
> >>>>>>>>>>> Packages
> >>>>>>>>>>> [ x ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF
> >>> and
> >>>>>>>>>>> Incubator Policy
> >>>>>>>>>>> [ x ] CHANGELOG included with release distribution
> >>>>>>>>>>> [ x ] New source code (React app, OpenTelemetry Ex) has
> >>>> compatible
> >>>>>>>>>>> licenses (ALv2, MIT)
> >>>>>>>>>>> [ x ] All Source Files Have Correct ASF Headers (ran RAT
> >> tool:
> >>>> only
> >>>>>>>>>>> .gitignore and .babelrc (json) exclude headers)
> >>>>>>>>>>> [ x ] No Binary Files in Source Release Packages (except for
> >>>>>> supporting
> >>>>>>>>>>> .png files)
> >>>>>>>>>>>
> >>>>>>>>>>>> On Apr 10, 2022, at 1:36 PM, Joshua Poore <
> >> poor...@apache.org
> >>>>
> >>>>>> wrote:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Please VOTE on the Apache Flagon (Incubating) UserALE.js
> >> 2.3.0
> >>>>>> Release
> >>>>>>>>>>> Candidate # 01.
> >>>>>>>>>>>>
> >>>>>>>>>>>> About Flagon: http://flagon.incubator.apache.org/
> >>>>>>>>>>>>
> >>>>>>>>>>>> This Minor release includes:
> >>>>>>>>>>>>
> >>>>>>>>>>>> Fixes issue in autostart configurations and start(), stop()
> >>>> export
> >>>>>>>>> usage
> >>>>>>>>>>>> Adds additional unit tests for autostart configurations
> >>>>>>>>>>>> Adds React App.js example/test utility
> >>>>>>>>>>>> Adds additional examples (non-user log examples)
> >>>>>>>>>>>> Minor updates to update deprecated downstream dev
> >> dependencies
> >>>>>>>>>>>> Minor changes to documentation, updated examples
> >>>>>>>>>>>>
> >>>>>>>>>>>> Resolved issues:
> >>>>>>>>>>>
> >>> https://github.com/apache/incubator-flagon-useralejs/projects/9
> >>>>>>>>>>>>
> >>>>>>>>>>>> Git source tag (566b279;
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.3.0-RC-01
> >>>>>>>>>>> )
> >>>>>>>>>>>>
> >>>>>>>>>>>> Staging repo:
> >>>>>> https://dist.apache.org/repos/dist/dev/incubator/flagon/
> >>>>>>>>>>>>
> >>>>>>>>>>>> Source Release Artifacts:
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.3.0-RC-01/
> >>>>>>>>>>>>
> >>>>>>>>>>>> PGP release keys (signed using F9374FAE3FCADF6E):
> >>>>>>>>>>>
> >>> https://dist.apache.org/repos/dist/release/incubator/flagon/KEYS
> >>>>>>>>>>>>
> >>>>>>>>>>>> Link to Successful CI Build:
> >>>>>>>>>>>
> >>>>> https://github.com/apache/incubator-flagon-useralejs/runs/5958813955
> >>>>>>>>>>>>
> >>>>>>>>>>>> Reference to the UserALE.js testing framework to assist in
> >>> your
> >>>>> unit
> >>>>>>>>> and
> >>>>>>>>>>> integration tests:
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Release+Management+Procedure
> >>>>>>>>>>>>
> >>>>>>>>>>>> I checked:
> >>>>>>>>>>>>
> >>>>>>>>>>>> [ x ] Build and Unit Tests Pass
> >>>>>>>>>>>> [ x ] Integration Tests Pass (Example Page, Webpack (NPM),
> >>> React
> >>>>>> (NPM)
> >>>>>>>>>>>> [ x ] "Incubating" in References to Project and Distribution
> >>>> File
> >>>>>> Names
> >>>>>>>>>>>> [ x ] Signatures and Hashes Match Keys
> >>>>>>>>>>>> [ x ] DISCLAIMER, LICENSE, and NOTICE Files in Source and
> >>> Binary
> >>>>>>>>> Release
> >>>>>>>>>>> Packages
> >>>>>>>>>>>> [ x ] DISCLAIMER, LICENSE, and NOTICE are consistent with
> >> ASF
> >>>> and
> >>>>>>>>>>> Incubator Policy
> >>>>>>>>>>>> [ x ] CHANGELOG included with release distribution
> >>>>>>>>>>>> [ x ] New source code (React app, OpenTelemetry Ex) have
> >>>>> compatible
> >>>>>>>>>>> licenses (ALv2, MIT)
> >>>>>>>>>>>> [ x ] All Source Files Have Correct ASF Headers (ran RAT
> >> tool:
> >>>>> only
> >>>>>>>>>>> .gitignore and .babelrc (json) exclude headers)
> >>>>>>>>>>>> [ x ] No Binary Files in Source Release Packages (except for
> >>>>>> supporting
> >>>>>>>>>>> .png files)
> >>>>>>>>>>>>
> >>>>>>>>>>>> Vote will be open for 72 hours. Please VOTE as follows:
> >>>>>>>>>>>>
> >>>>>>>>>>>> [ ] +1, let's get it released!!!
> >>>>>>>>>>>> [ ] +/-0, fine, but consider to fix few issues before...
> >>>>>>>>>>>> [ ] -1, nope, because... (and please explain why)
> >>>>>>>>>>>>
> >>>>>>>>>>>> Along with your VOTE, please indicate testing and checks
> >>> you've
> >>>>> made
> >>>>>>>>>>> against build artifacts, src, and documentation:
> >>>>>>>>>>>>
> >>>>>>>>>>>> [ ] Build and Unit Tests Pass
> >>>>>>>>>>>> [ ] Integration Tests Pass
> >>>>>>>>>>>> [ ] "Incubating" in References to Project and Distribution
> >>> File
> >>>>>> Names
> >>>>>>>>>>>> [ ] Signatures and Hashes Match Keys
> >>>>>>>>>>>> [ ] DISCLAIMER, LICENSE, and NOTICE Files in Source and
> >> Binary
> >>>>>> Release
> >>>>>>>>>>> Packages
> >>>>>>>>>>>> [ ] DISCLAIMER, LICENSE, and NOTICE are consistent with ASF
> >>> and
> >>>>>>>>>>> Incubator Policy
> >>>>>>>>>>>> [ ] CHANGELOG included with release distribution
> >>>>>>>>>>>> [ ] All Source Files Have Correct ASF Headers
> >>>>>>>>>>>> [ ] No Binary Files in Source Release Packages
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thank you to everyone that is able to VOTE as well as
> >> everyone
> >>>>> that
> >>>>>>>>>>> contributed to Apache Flagon UserALE.js 2.3.0!
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>

Reply via email to