> On Jul 21, 2016, at 2:03 PM, Peter TB Brett <peter.br...@livecode.com> wrote: > > On 21/07/2016 15:08, Colin Holgate wrote: > >> 2. It could be worth changing the title to OS X / macOS, and >> including version 10.12 in the list. I know that it’s not released, >> but it is in public beta, and I’m pretty sure you intend to support >> it. LiveCode seems to be running well in 10.12. >> >> As far as I can tell LiveCode apps run under iOS 10 ok too, which >> again is not released, but would there be any harm in stating now >> that you intend to support it? > > Thank you for bringing it up, since clearly some clarification is needed! > > We do not currently intend to officially support beta releases of Mac OS > or Mac OS X or iOS. When I say this, I mean that we would like to know > if there are any problems, and we will certainly investigate > problems promptly; however, beta and/or preview releases are not included in > the list of tests that must pass in order to release LiveCode, and we can't > commit to providing technical support if you run into problems. > > LiveCode might well run fine on these preview releases! However, until Apple > releases a version of Mac OS 10.12 to general availability, using LiveCode on > it will not be officially supported. Realistically, we need time to get our > systems and staff up to speed! > > I can happily state that we intend to extend official support to any new > stable releases of OS X / Mac OS / iOS that Apple come out with. So, since > 10.12 stable isn't out yet, it's not yet supported. I will clarify the text > in the blog post. > > Note that Ubuntu Linux 16.10 alpha, and Fedora Linux "Rawhide", and Debian > Unstable, and Android N previews and Windows <next version here> are all > _also_ not officially supported. But LiveCode, and apps made with it, may > very well work perfectly on any or all of them! > > I hope that clarifies the situation. Please let me know if you have any > further questions or concerns. > > Peter
While I understand why you might want to limit support to “released” OSes, I would say that LC needs to checking against each “early” release, looking for issues and checking for new features that might be supported. LC should take bug reports against these early releases and, while maybe not acting right away on them, making sure that as they approach release status, those bugs get fixed. As a development tool it is imperative that LC be ready for a new OS release. If there is a change that breaks a LC app with a new OS release, it is imperative that LC be updated and ready to go so the developer can release an updated app on day one. Having to wait weeks or longer to update your LC app after the “Official” release of an OS makes the developer and their app look bad at best. Both Apple and Microsoft (and any linux tools I’m sure) make sure that their tools support these early releases so that developers can keep their apps updated and ready as well as take advantage of any new features and technology that they are adding. By NOT keeping LC updated in the same fashion, LC becomes a second class citizen and choice for development. I really can’t stress this enough. Use VM’s, don’t mess with your production systems, but have LC ready for whatever NEW OS that LC supports when it comes out. Best, Steve MacLean _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
