My $0.02: Royale has bee production ready for years. We probably should have switched to 1.0 and beyond a long time ago.
Let’s just do it. FWIW, some of the things I’m itching to work on: 1. Support for Tailwind. I want to do research into how that works and brainstorm on how we can best support it. 2. Compiler speed improvements. I’d like to experiment with AI agents to see if we can get some easy wins with that. If should be an interesting experiment. 3. Similarly, some of the agents are good at porting code. It would be interesting to let an agent loose o trying for port the compiler from Javato something else. (Rust maybe?) 4. Some time back I started on a runtime Markdown renderer with class mapping to Royale classes. I’d like to finish that. I’m going to try to update some of the typedefs before this release. Maybe of the typedefs are very outdated. Harbs > On Jan 31, 2026, at 3:43 PM, Andrew Wetmore <[email protected]> wrote: > > On Sat, Jan 31, 2026 at 7:08 AM Hugo Ferreira <[email protected]> > wrote: > >> As someone who has been using Apache Royale *daily in production for many >> years*, I’ll be honest: at this point, the version number has become >> largely irrelevant to me. >> > > For those who have contributed to Royale getting to where it is today, and > who use it regularly, the release number is the probably least important > detail. > > But this is about the least-expensive step we can take to raise our > visibility a little bit among those who used to use Royale and moved away; > are in the AS3 universe but never tried Royale; or might become curious, no > matter what their tech position, as we reach this 'milestone.' Our number > of contributors and committers has remained pretty static for lots of years > (we recently got a query from the Board about what we are doing to bring in > more active folks), and it would be cool if we could see activity from four > or five more people to augment what the inmates are doing now. > > Does naming the release require a vote? I have not seen any comments > opposed to the next release being 1.0.0, so we could go with lazy consensus. > > a > > > > > > > Andrew Wetmore > Assistant VP, Marketing and Publicity, The ASF <https://apache.org> > Editor-Writer, Infra team, The ASF > > Editor, moosehousepress.com > > > >> >> > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
