Hi all,
Well theoretically for example Greg - who noted he'll be able to do a review
soon - could theoretically do the review and find something you folks didn't.
So I would suggest to keep the vote open for the 72 hours ... especially as you
announced the votes to stay open for 72 hours.
Was just jumping in from the side-lines, just in case you just overlooked this.
Chris
Am 15.04.20, 11:02 schrieb "Carlos Rovira" <carlosrov...@apache.org>:
Hi Chris,
unless this is against some Apache rules the vote thread state this:
"This vote will be open for 72 hours or until a result can be called.
The vote passes if there is:
- At least 3 +1 votes from the PMC
- More positive votes than negative votes"
So this seems ok, right?
Thanks
Carlos
El mié., 15 abr. 2020 a las 10:47, Yishay Weiss (<yishayj...@hotmail.com>)
escribió:
> Hi Chris,
>
> I may have made a mistake here, but I thought it was ok since we had
> enough +1 votes. As I understood it, that’s a sufficient condition. Trying
> to speed things up, but my apologies if this somehow compromises Apache
> rules.
>
> Thanks,
> Yishay
>
> From: Christofer Dutz<mailto:christofer.d...@c-ware.de>
> Sent: Wednesday, April 15, 2020 11:31 AM
> To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> Subject: Re: [DISCUSS] Discuss Release Apache Royale 1.2.0
>
> Royale not sticking to the typical 72 hour voting timeframe?
>
> Chris
>
> Am 15.04.20, 10:29 schrieb "Carlos Rovira" <carlosrov...@apache.org>:
>
> Hi Yishay,
>
> build tools and jburg was never released on its own before. Always was
> part
> of the global royale release. This is the first time we do this.
>
> Thanks
>
> El mié., 15 abr. 2020 a las 10:21, Yishay Weiss (<
> yishayj...@hotmail.com>)
> escribió:
>
> > I’ve just noticed the subject should be changed to
> >
> > [DISCUSS] Release Apache Royale Compiler Build Tools 1.2.0. Looks
> like a
> > bug in CI step 6.
> >
> > Anyway, the vote has passed. I haven’t seen previous announcements
on
> > compiler build tools. Has this been done in the past? Can anyone
> point me
> > to an example?
> >
> > Thanks.
> >
> > From: Greg Dove<mailto:greg.d...@gmail.com>
> > Sent: Tuesday, April 14, 2020 9:27 PM
> > To: Apache Royale Development<mailto:dev@royale.apache.org>
> > Subject: Re: [DISCUSS] Discuss Release Apache Royale 1.2.0
> >
> > fyi I can't get to this until my current EOD, about 12 hours from
> now. I
> > will remind myself what I need to do and check it then and vote, if
> the
> > voting is still open (I understand it may not be, as I think the
> threshold
> > was already passed).
> >
> >
> >
> > On Wed, Apr 15, 2020 at 6:03 AM Carlos Rovira <
> carlosrov...@apache.org>
> > wrote:
> >
> > > Remember that we have Maven Wrapper [1] in our repo so if you
> don't have
> > > maven installed you can just use "mvnw" (Mac) or "mvnw.cmd" (Win)
> and
> > that
> > > will install maven for you :)
> > >
> > > [1] https://github.com/takari/maven-wrapper
> > >
> > > El mar., 14 abr. 2020 a las 18:05, Josh Tynjala (<
> > > joshtynj...@bowlerhat.dev>)
> > > escribió:
> > >
> > > > If you're on Windows, and you happened to install Maven using
the
> > > > Chocolatey package manager, you may need to tweak the
> > > ApproveBuildTools.xml
> > > > file to get it to work.
> > > >
> > > > Find this line:
> > > >
> > > > <condition property="mvn" value="mvn.cmd">
> > > >
> > > > And change it to this:
> > > >
> > > > <condition property="mvn" value="mvn.exe">
> > > >
> > > > I think that most people will be fine, but I just wanted to
> mention it.
> > > >
> > > > --
> > > > Josh Tynjala
> > > > Bowler Hat LLC <https://bowlerhat.dev>
> > > >
> > > >
> > > > On Mon, Apr 13, 2020 at 1:33 PM <apacheroyal...@gmail.com>
> wrote:
> > > >
> > > > > This is the discussion thread.
> > > > >
> > > > > Thanks,
> > > > > Yishay Weiss
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira
> > >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
