> So far, we have not had the release scripts properly generate the right > version number for the NPM artifacts.
This spurred a question for me. Is there a way to find out what version number the SDK binaries are in code for Royale? Sort of like the Flex SDK mx.core.FlexVersion or at least a build date? -Mark K -----Original Message----- From: Alex Harui [mailto:[email protected]] Sent: Friday, April 26, 2019 2:44 AM To: [email protected] Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0 I do not have an opinion on what technical/marketing criteria we use to decide which release to call 1.0. I'm not working directly with users/customers. I do not currently have time/energy/budget to work on any of the things folks think need to be done to get to 1.0 and barely have enough time to work on getting the next release out. So someone else will have to supply the time/energy/budget to get these tasks done. I do have an opinion based on a practical aspect. So far, we have not had the release scripts properly generate the right version number for the NPM artifacts. That's why we've jumped from 0.9.4 to 0.9.6 and skipped 0.9.5. So I would say we should not call this next release 1.0 and wait until the release automation can correctly version all artifacts with the right version number before we pick one to call 1.0. With any luck I'll get the automation running next week and will ask for someone to volunteer to test drive it. -Alex
