Hi Everyone,
As the 72 hours period has come and gone I would like to bring this thread to a
close.
The Apache Flagon Community has voted [+6] to release Apache Flagon
(Incubating) 2.0.1. The VOTE has passed, having received the necessary +3
binding VOTEs from PPMC/IPMC members.
Detailed
I thinks that’s great for this patch release.
Down the line, I’d love it if we could do an end to end integration test with
the mentors to identify any thoughts about how to make deployment easier and
more adoptable from either technical or instructive perspective
(Documentation)—see the
All,
Sorry for my delay!
Given that the extent of my knowledge of js is that it stands for
javascript (I think?)...what can I do to help with the release
decisions and/or the incubator process?
I ran npm install and didn't get any scary dependency vulnerability
messages (after getting the
+1
On Fri, Aug 2, 2019 at 8:40 AM Laura Mariano wrote:
>
> +1
>
> On Tue, Jul 30, 2019, 10:46 PM Joshua Poore wrote:
>
> >
> > Hi Folks,
> >
> > Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate # 1.
> >
> > About Flagon: http://flagon.incubator.apache.org/
> >
> > This
+1
On Tue, Jul 30, 2019, 10:46 PM Joshua Poore wrote:
>
> Hi Folks,
>
> Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate # 1.
>
> About Flagon: http://flagon.incubator.apache.org/
>
> This (patch) release includes :
>
> 1. Updates to package.json and package-lock.json to
Hi Furkan,
Let’s follow up with this, the example server with the example page is pretty
reliable. FLAGON-169 has more to do with mixed-media issues arising from the
use of our browser plugin.
I’ll follow up with you in a separate thread.
> On Aug 1, 2019, at 4:40 PM, Furkan KAMACI wrote:
+1
> On Aug 1, 2019, at 4:40 PM, Furkan KAMACI wrote:
>
> Hi,
>
> +1 from me.
>
> I checked:
> - Incubating in name
> - Disclaimer exists
> - LICENSE is fine
> - NOTICE is fine
> - No unexpected binary files
> - Code compiles and tests successfully run
>
> On the other hand, I've tried to
+1
On Thu, Aug 1, 2019, 4:40 PM Furkan KAMACI wrote:
> Hi,
>
> +1 from me.
>
> I checked:
> - Incubating in name
> - Disclaimer exists
> - LICENSE is fine
> - NOTICE is fine
> - No unexpected binary files
> - Code compiles and tests successfully run
>
> On the other hand, I've tried to run
Hi,
+1 from me.
I checked:
- Incubating in name
- Disclaimer exists
- LICENSE is fine
- NOTICE is fine
- No unexpected binary files
- Code compiles and tests successfully run
On the other hand, I've tried to run example but could not see the event
logs at terminal. Accessing to a file is
Hello,
On Wed, 31 Jul 2019 at 03:46, Joshua Poore wrote:
> Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate # 1.
>
> 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...
> [
Hi Folks,
Please VOTE on the Apache Flagon (Incubating) v2.0.1 Release Candidate # 1.
About Flagon: http://flagon.incubator.apache.org/
This (patch) release includes :
1. Updates to package.json and package-lock.json to resolve downstream
Prototype Pollution vulnerabilities in dev
11 matches
Mail list logo
