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
