+1

On Thu, Jun 13, 2019, 9:17 AM Rob Foley <[email protected]> wrote:

> +1
>
> On Wed, Jun 12, 2019 at 11:36 PM Joshua Poore <[email protected]> wrote:
>
> > Hi Folks,
> >
> > Mentors say safe bet is to do re-release of UserALE.js 1.0.0 under strict
> > release process. As such I am calling a VOTE:
> >
> > Please VOTE on the Apache FLAGON UserALE.js 1.0.0 Release Candidate #3.
> >
> > We solved 50 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550&styleName=Text&projectId=12320621&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7Cd2c9eccb98c0590b13b40b9d863a18bfc463546f%7Clin
> > <
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341550&styleName=Text&projectId=12320621&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED|d2c9eccb98c0590b13b40b9d863a18bfc463546f|lin
> > >
> >
> > Git source tag (d99ad9a2757fb5e412437227c6f9508d06c192e1):
> >
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
> > <
> >
> https://github.com/apache/incubator-flagon-useralejs/releases/tag/1.0.0r-RC3_06_12_2019
> > >
> >
> > Source Release Branch:
> >
> https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease
> > <
> https://github.com/apache/incubator-flagon-useralejs/tree/v1.0.0ReRelease>
> >
> >
> > Source Release Candidate Artifacts:
> > https://dist.apache.org/repos/dist/dev/incubator/flagon/ <
> > https://dist.apache.org/repos/dist/dev/incubator/flagon/>
> >
> > PGP release keys (signed using 48BAEBF6):
> > https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS <
> > https://dist.apache.org/repos/dist/dev/incubator/flagon/KEYS> (new keys
> > must must be copied over to http://apache.org/dist/incubator/flagon/ <
> > http://apache.org/dist/incubator/flagon/>)
> >
> > Vote will be open for 72 hours.
> >
> > Thank you to everyone that is able to VOTE as well as everyone that
> > contributed to Apache FLAGON 1.0.0 & 1.0.0r.
> >
> > [ ] +1, let's get it released!!!
> > [ ] +/-0, fine, but consider to fix few issues before...
> > [ ] -1, nope, because... (and please explain why)
>

Reply via email to