Hi I would agree with Justin here, my only addition would be that when we hit 1.0 status, some of the APIs should become immutable – for example things like BinaryData and so on, should not then be changed later on. If you have an application which compiles against Royale 1.0, it should also compile (and work) against any later release (at least 1.x release perhaps; compatibility doesn’t necessarily have to go across major versions?).
The component libraries and new functionality can always be added, so 1.0 isn’t a “final” version, it just means that you can go ahead without having to make changes because someone has updated an API leaving you with code that no longer compiles. I also agree that Royale isn’t the easiest thing to get started with .. so #2 and #3 below are pretty key. We can help with #7 if anyone needs support :-) thanks Andrew From: Justin M. Hill [mailto:jus...@prominic.net] Sent: 24 April 2019 20:21 To: dev@royale.apache.org Subject: [EXTERNAL] RE: Let's bump Royale version to 1.0 I agree with Piotr. Perception matters. 1.0 does not need to be perfect, it just needs to be good enough. And Royale is good enough to be called 1.0 in my opinion. It has 2 production applications -- ones from Harbs and Carlos are already running on it from what I understand. Royale needs to get traction in the market. Many people will not pay attention until the following items occur: 1) A version 1.0 is released 2) There are clear tutorials which can get people started quickly [the Moonshine team has agreed to fund a few videos to get this started] 3) It is very easy for new developers to get started with the technology [the Moonshine IDE accomplishes this with first class support for Royale, Flex, and ActionScript] 3) Documentation is improved, easy to read, friendly, and up-to-date 4) Marketing ensues explaining why people should look at Royale compared to React, ExtJS, Angular, etc. If these articles can get written, the Moonshine IDE team is willing to help fund some Google and other campaigns to bring traction. 5) Multiple IDEs support Royale well -- not just Moonshine IDE and Visual Studio Code. Eclipse, IntelliJ, FlashDevelop also all need to support Royale. 6) Testimonials from other companies who have ported Flex or created fresh Royale applications become commonplace and trust starts to build that the conversion is possible 7) A consulting ecosystem needs to exist where it is fast for newcomers / explorers to decide the technology is worth pursuing and want to engage with a consultant to help them along the journey. Of the above items, the first and easiest thing to control is whether we call the software 1.0 or not. I last had this discussing 28 months ago with Alex in Seattle. A huge amount of work has gone into Royale since then. As the saying goes: the enemy of good enough is perfection. Please, consider pushing the release to 1.0. Thank you, Justin Hill [Inactive hide details for dev-digest-help---04/24/2019 08:33:01 AM---dev Digest 24 Apr 2019 13:32:50 -0000 Issue 1958 Topics (m]dev-digest-help---04/24/2019 08:33:01 AM---dev Digest 24 Apr 2019 13:32:50 -0000 Issue 1958 Topics (messages 9856 through 9859) ----- Message from Piotr Zarzycki <piotrzarzyck...@gmail.com<mailto:piotrzarzyck...@gmail.com>> on Wed, 24 Apr 2019 11:56:47 +0200 ----- To: dev@royale.apache.org<mailto:dev@royale.apache.org> Subject: Let's bump Royale version to 1.0 Hi Team, Lately, I’m working with Royale framework more and more. Once you know the framework better from the inside your productivity skyrockets and it is similar to what we had in Flex. The question comes up - why do we actually cannot bump our version to 1.0? I’d like to see that happen with the upcoming release or at least the following one. What’s holding us back? Is it lack of features? What if I don’t have some feature in 1.0, but I will add it in 1.1? This is still fine in my opinion. Or is it bugs? Because guess how people are seeing us after 5 years of development and still with leading 0. They think “highly unstable”. And because this continues for so long they think the project might, in fact, be dead. I would like to ask you Team to consider making our upcoming version (or the following one) as 1.0. Let’s find the answer in this thread. Post your arguments: “Why not?”, “Why yes?” Thanks, -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki<https://clicktime.symantec.com/3MX5snbQLPuKXoDCHV8C8sh7Vc?u=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki> <https://www.patreon.com/piotrzarzycki<https://clicktime.symantec.com/3MX5snbQLPuKXoDCHV8C8sh7Vc?u=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki>>*
