What's obvious about March and schedules?

Is this just one of those things we're  'supposed to know', like how to
pronounce Edinburgh properly?

On Sun, Mar 10, 2013 at 11:21 AM, Richmond <richmondmathew...@gmail.com>wrote:

> On 03/10/2013 07:31 PM, Ian Wood wrote:
>
>> 'Once we get through that planning we'll be working away to bring you the
>> "as is" open source release of the platform. We promised March for that and
>> for anyone unfamiliar with software schedules, that means the end of March.'
>>
>
> Oo, a bit sn*tty methinks.
>
> As someone familiar with software schedules I am well aware that a very
> large proportion of them miss "the end of March",
> unforeseen factors slowing things down.
>
> That, of itself, is not a source of worry, what is is that that one of the
> ways of keeping the punters happy is by constantly drip-feeding
> them gobbets of information so that they feel they are not being excluded
> from the development process.
>
>
>
>> http://blog.runrev.com/blog/**bid/272739/We-Kickstarted-**LiveCode<http://blog.runrev.com/blog/bid/272739/We-Kickstarted-LiveCode>
>>
>> Ian
>>
>> On 10 Mar 2013, at 12:43, Richmond wrote:
>>
>>  The plan was for the "as is" version of Open Source Livecode to
>>> be released at the end of March . . .
>>>
>>> . . . wondering if anyone can confirm this as have plans that are
>>> dependent on the release date.
>>>
>>> Richmond.
>>>
>>

Stephen Barncard
San Francisco Ca. USA

more about sqb  <http://www.google.com/profiles/sbarncar>
_______________________________________________
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

Reply via email to