I agree on a point where we need more people who can easily do a release.
Let’s have 2 more releases with someone else than you and discuss 1.0 than.
In case of announcing I think it should happen once all release related
stuff is fully done. We need to update website and Tour de Jewel build
No, the links seem to be valid.
On Sun, May 28, 2023 at 9:52 AM Yishay Weiss wrote:
> Thanks, Andrew. Do the links need to reflect the transition from mirrors
> somehow?
>
> From: Andrew Wetmore
> Sent: Sunday, May 28, 2023 3:44 PM
> To: dev@royale.apache.org
Thanks, Andrew. Do the links need to reflect the transition from mirrors
somehow?
From: Andrew Wetmore
Sent: Sunday, May 28, 2023 3:44 PM
To: dev@royale.apache.org
Subject: Re: [DRAFT][ANNOUNCE] Apache Royale 0.9.10 released
I think this is very clear and
I think this is very clear and hopeful.
Two notes: The ASF has retired its mirror system, and is moving away from
prominent use of "Apache", usually in favour of "The ASF". This is in
response to concerns about appropriation of images (feather) and mythos
(noble Indians) without consultation or
I think it's a good idea to bump the next version, maybe to 0.9.12. Going to
1.0 now does not seem like a good idea to me, because it would involve some
overhead and my aim now is to get somebody else in the team involved in the
next release and I want to keep it simple for him or her.
I just
The Apache Royale community is pleased to announce the release of Apache
Royale 0.9.10.
The Apache Royale project is the next generation of the Apache Flex SDK. It
lets developers use MXML and ActionScript 3 to generate HTML/JS/CSS
applications which can run natively in browsers. The
My suggestion is next release 1.0.0 finally and forgot about that minor
stuff.
The other thing let’s have clear explanation in announcement.
On Sun, 28 May 2023 at 11:52, Yishay Weiss wrote:
> OTOH the release number is incorrect. I published it to 0.9.11
> accidentally. I'm afraid I cannot
OTOH the release number is incorrect. I published it to 0.9.11 accidentally.
I'm afraid I cannot change that to 0.9.10 because I accidentally published to
0.9.10 a year ago. The good news is that I have fixed the npm release script so
this issue should not happen again. The bad news is that
