No big deal, I just wanted to make sure that the posted update was not actually 6.6.2.
Bob S On Sep 26, 2014, at 11:38 , Fraser Gordon <fraser.gor...@livecode.com> wrote: > On 26/09/2014 19:24, la...@significantplanet.org wrote: >> Hi Bob, >> I had the exact same experience that you did. >> I just assumed it was a display bug with LC and ignored it. When I got >> the alert about 6.6.3, I just chose "Skip this version." >> Maybe you or someone will report it as a bug. >> Larry > That's exactly what it is - a minor bug caused by an oversight on my > part (I forgot to update the version information file on the Windows > build machine). Given the relative urgency of getting 6.6.3 out, it > didn't seem worthwhile delaying the release (it would have been all > platforms because the standalone engine version is wrong too). > > If you submit a bug report, it would immediately get set to > AWAITING_BUILD; after all, it will be fixed in the next build ;) > > Regards, > Fraser > > > _______________________________________________ > 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 _______________________________________________ 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
