[RESULT] Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-03-03 Thread Joshua Poore
Thanks to all who participated in the VOTE to Release Apache Flagon UserALE.js 
(Incubating) 2.1.0

Results are as follows:

[ ] +1, let's get it released!!!

Furkan KAMACI (Binding)
Tim Allison (Binding)
Dave Meikle (Binding)
Rob Foley
Joshua Poore

[ 0 ] +/-0, fine, but consider to fix few issues before...
[ 0 ] -1, nope, because... (and please explain why)

The VOTE Passes! Thanks, again!

Josh
 

> On Mar 2, 2020, at 8:35 AM, Furkan KAMACI  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
> 
> PS: Should it be Copyright 2019-2020 The Apache Software Foundation at
> NOTICE file?
> 
> Kind Regards,
> Furkan KAMACI
> 
> On Mon, Feb 24, 2020 at 4:39 PM Tim Allison  wrote:
> 
>> +1
>> Late as well...sorry!
>> 
>> 
>> 
>> On Sat, Feb 22, 2020 at 8:19 PM Joshua Poore 
>> wrote:
>> 
>>> Hi All,
>>> 
>>> REMINDER: Please VOTE on the Apache Flagon 2.1.0 Release.
>>> 
>>> Thanks,
>>> 
>>> Josh
>>> 
 On Feb 14, 2020, at 10:33 AM, Rob Foley  wrote:
 
 A bit late, but +1:
 
 [x] Build and Unit Tests Pass
 [x] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
 Packages
 [x] Signatures and Hashes Match Keys
 [x] CHANGELOG included with release distribution
 
 On Mon, Feb 10, 2020 at 9:14 PM Joshua Poore 
>>> wrote:
 
> pushed updated webpack.config.js that includes ALv2 header
> 
>> On Feb 10, 2020, at 7:34 PM, Joshua Poore 
> wrote:
>> 
>> Disregard. You’re right. webpack config is .js. Missed that.
>> 
>> You see any issues with our disclaimer given that the webpack config
> doesn’t have a header?
>> 
>> Joshua Poore
>> 
>> 
>>> On Feb 10, 2020, at 7:32 PM, Joshua Poore 
> wrote:
>>> 
>>> Hi Dave,
>>> 
>>> Thanks for identifying! I thought comments aren’t supported in JSON.
> There are custom libs for doing that, but I doubt node and web pack
>> can
> call them.
>>> 
>>> If you can point me to an example, I’ll get it in there.
>>> 
>>> Joshua Poore
>>> 
>>> 
>> On Feb 10, 2020, at 5:03 PM, David Meikle 
>> wrote:
>> On Fri, 7 Feb 2020 at 23:12, Joshua Poore 
> wrote:
>> Hi Folks,
>> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
>> Source Release Artifacts:
>> 
> 
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
>> <
>> 
> 
>>> 
>> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
>> 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)
 +1 (binding) : Performed the check list provided on the source
>>> release
 package.
 There are some files, like the webpack.config.js, flagged by Apache
>>> RAT
 that we could put an AL header on. Not a deal breaker, but worth
 considering.
 Cheers,
 Dave
>> 
> 
> 
>>> 
>>> 
>> 



Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-03-02 Thread Furkan KAMACI
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

PS: Should it be Copyright 2019-2020 The Apache Software Foundation at
NOTICE file?

Kind Regards,
Furkan KAMACI

On Mon, Feb 24, 2020 at 4:39 PM Tim Allison  wrote:

> +1
> Late as well...sorry!
>
>
>
> On Sat, Feb 22, 2020 at 8:19 PM Joshua Poore 
> wrote:
>
> > Hi All,
> >
> > REMINDER: Please VOTE on the Apache Flagon 2.1.0 Release.
> >
> > Thanks,
> >
> > Josh
> >
> > > On Feb 14, 2020, at 10:33 AM, Rob Foley  wrote:
> > >
> > > A bit late, but +1:
> > >
> > > [x] Build and Unit Tests Pass
> > > [x] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
> > > Packages
> > > [x] Signatures and Hashes Match Keys
> > > [x] CHANGELOG included with release distribution
> > >
> > > On Mon, Feb 10, 2020 at 9:14 PM Joshua Poore 
> > wrote:
> > >
> > >> pushed updated webpack.config.js that includes ALv2 header
> > >>
> > >>> On Feb 10, 2020, at 7:34 PM, Joshua Poore 
> > >> wrote:
> > >>>
> > >>> Disregard. You’re right. webpack config is .js. Missed that.
> > >>>
> > >>> You see any issues with our disclaimer given that the webpack config
> > >> doesn’t have a header?
> > >>>
> > >>> Joshua Poore
> > >>>
> > >>>
> >  On Feb 10, 2020, at 7:32 PM, Joshua Poore 
> > >> wrote:
> > 
> >  Hi Dave,
> > 
> >  Thanks for identifying! I thought comments aren’t supported in JSON.
> > >> There are custom libs for doing that, but I doubt node and web pack
> can
> > >> call them.
> > 
> >  If you can point me to an example, I’ll get it in there.
> > 
> >  Joshua Poore
> > 
> > 
> > >>> On Feb 10, 2020, at 5:03 PM, David Meikle 
> wrote:
> > >>> On Fri, 7 Feb 2020 at 23:12, Joshua Poore 
> > >> wrote:
> > >>> Hi Folks,
> > >>> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
> > >>> Source Release Artifacts:
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> > >>> <
> > >>>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> > >>> 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)
> > > +1 (binding) : Performed the check list provided on the source
> > release
> > > package.
> > > There are some files, like the webpack.config.js, flagged by Apache
> > RAT
> > > that we could put an AL header on. Not a deal breaker, but worth
> > > considering.
> > > Cheers,
> > > Dave
> > >>>
> > >>
> > >>
> >
> >
>


Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-02-24 Thread Tim Allison
+1
Late as well...sorry!



On Sat, Feb 22, 2020 at 8:19 PM Joshua Poore  wrote:

> Hi All,
>
> REMINDER: Please VOTE on the Apache Flagon 2.1.0 Release.
>
> Thanks,
>
> Josh
>
> > On Feb 14, 2020, at 10:33 AM, Rob Foley  wrote:
> >
> > A bit late, but +1:
> >
> > [x] Build and Unit Tests Pass
> > [x] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
> > Packages
> > [x] Signatures and Hashes Match Keys
> > [x] CHANGELOG included with release distribution
> >
> > On Mon, Feb 10, 2020 at 9:14 PM Joshua Poore 
> wrote:
> >
> >> pushed updated webpack.config.js that includes ALv2 header
> >>
> >>> On Feb 10, 2020, at 7:34 PM, Joshua Poore 
> >> wrote:
> >>>
> >>> Disregard. You’re right. webpack config is .js. Missed that.
> >>>
> >>> You see any issues with our disclaimer given that the webpack config
> >> doesn’t have a header?
> >>>
> >>> Joshua Poore
> >>>
> >>>
>  On Feb 10, 2020, at 7:32 PM, Joshua Poore 
> >> wrote:
> 
>  Hi Dave,
> 
>  Thanks for identifying! I thought comments aren’t supported in JSON.
> >> There are custom libs for doing that, but I doubt node and web pack can
> >> call them.
> 
>  If you can point me to an example, I’ll get it in there.
> 
>  Joshua Poore
> 
> 
> >>> On Feb 10, 2020, at 5:03 PM, David Meikle  wrote:
> >>> On Fri, 7 Feb 2020 at 23:12, Joshua Poore 
> >> wrote:
> >>> Hi Folks,
> >>> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
> >>> Source Release Artifacts:
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> >>> <
> >>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> >>> 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)
> > +1 (binding) : Performed the check list provided on the source
> release
> > package.
> > There are some files, like the webpack.config.js, flagged by Apache
> RAT
> > that we could put an AL header on. Not a deal breaker, but worth
> > considering.
> > Cheers,
> > Dave
> >>>
> >>
> >>
>
>


Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-02-14 Thread Rob Foley
A bit late, but +1:

[x] Build and Unit Tests Pass
[x] DISCLAIMER, LICENSE, and NOTICE Files in Source and Binary Release
Packages
[x] Signatures and Hashes Match Keys
[x] CHANGELOG included with release distribution

On Mon, Feb 10, 2020 at 9:14 PM Joshua Poore  wrote:

> pushed updated webpack.config.js that includes ALv2 header
>
> > On Feb 10, 2020, at 7:34 PM, Joshua Poore 
> wrote:
> >
> > Disregard. You’re right. webpack config is .js. Missed that.
> >
> > You see any issues with our disclaimer given that the webpack config
> doesn’t have a header?
> >
> > Joshua Poore
> >
> >
> >> On Feb 10, 2020, at 7:32 PM, Joshua Poore 
> wrote:
> >>
> >> Hi Dave,
> >>
> >> Thanks for identifying! I thought comments aren’t supported in JSON.
> There are custom libs for doing that, but I doubt node and web pack can
> call them.
> >>
> >> If you can point me to an example, I’ll get it in there.
> >>
> >> Joshua Poore
> >>
> >>
> > On Feb 10, 2020, at 5:03 PM, David Meikle  wrote:
> > On Fri, 7 Feb 2020 at 23:12, Joshua Poore 
> wrote:
> > Hi Folks,
> > Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
> > Source Release Artifacts:
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> > <
> >
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> > 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)
> >>> +1 (binding) : Performed the check list provided on the source release
> >>> package.
> >>> There are some files, like the webpack.config.js, flagged by Apache RAT
> >>> that we could put an AL header on. Not a deal breaker, but worth
> >>> considering.
> >>> Cheers,
> >>> Dave
> >
>
>


Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-02-10 Thread Joshua Poore
Disregard. You’re right. webpack config is .js. Missed that.

You see any issues with our disclaimer given that the webpack config doesn’t 
have a header?

Joshua Poore


> On Feb 10, 2020, at 7:32 PM, Joshua Poore  wrote:
> 
> Hi Dave,
> 
> Thanks for identifying! I thought comments aren’t supported in JSON. There 
> are custom libs for doing that, but I doubt node and web pack can call them. 
> 
> If you can point me to an example, I’ll get it in there.
> 
> Joshua Poore
> 
> 
 On Feb 10, 2020, at 5:03 PM, David Meikle  wrote:
 On Fri, 7 Feb 2020 at 23:12, Joshua Poore  wrote:
 Hi Folks,
 Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
 Source Release Artifacts:
 https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
 <
 https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
 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)
>> +1 (binding) : Performed the check list provided on the source release
>> package.
>> There are some files, like the webpack.config.js, flagged by Apache RAT
>> that we could put an AL header on. Not a deal breaker, but worth
>> considering.
>> Cheers,
>> Dave



Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-02-10 Thread David Meikle
On Fri, 7 Feb 2020 at 23:12, Joshua Poore  wrote:

> Hi Folks,
>
> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
>
> Source Release Artifacts:
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> <
> https://dist.apache.org/repos/dist/dev/incubator/flagon/apache-flagon-useralejs-incubating-2.1.0-RC-01/
> >
>
> 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)
>

+1 (binding) : Performed the check list provided on the source release
package.

There are some files, like the webpack.config.js, flagged by Apache RAT
that we could put an AL header on. Not a deal breaker, but worth
considering.

Cheers,
Dave


Re: [VOTE] Release Apache Flagon UserALE.js (Incubating) 2.1.0

2020-02-07 Thread Joshua Poore
+1

I checked the following:

[ 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

> On Feb 7, 2020, at 4:12 PM, Joshua Poore  wrote:
> 
> Hi Folks,
>  
> Please VOTE on the Apache Flagon 2.1.0 Release Candidate 01
>  
> About Flagon: http://flagon.incubator.apache.org/ 
> 
>  
> This {Major/Minor/Patch} release includes :
>  
>   • Module package-bundler deployment support (include UserALE.js via 
> 'import' & 'require')
>   • Updated existing example page to include a range of HTML elements
>   • New example page for including UserALE.js as a module (Webpack 
> example)
>   • Added support for logging from HTML Forms
>   • Added SessionId persistence via SessionStorage
>   • Exposes a wide range of functions to support custom logging with 
> UserALE.js
>   • Added support for passing auth-headers via log pipeline to back-end
>   • Added additional log fields: browser type and version, inner 
> width/height (for heatmaps)
>  
> We solved 31 issues: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345442=Text=12320621=Create_token=A5KQ-2QAV-T4JA-FDED_8301b4e9c1c91354ea85ab02c89ec979db077d9a_lin
>  
> 
>  
> Git source tag (7746500): 
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/2.1.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.1.0-RC-01/
>  
> 
>  
> PGP release keys (signed using F9374FAE3FCADF6E): 
> https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS 
> 
>  
> Link to Successful Jenkins Build: 
> https://builds.apache.org/job/useralejs-ci/101/ 
> 
>  
> Reference to UserALE.js testing framework to assist in verifying this 
> release: 
> https://cwiki.apache.org/confluence/display/FLAGON/UserALE.js+Testing+Framework
>  
> 
>  
> 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 2.1.0