By the same token, releasing early makes the assumption that significant
portions of the software in question are believed to operate correctly unless
stated otherwise. We could absolutely release CoApp "early" in its present
state, but I would only wish to do so with a disclaimer that we do no
On Thu, Oct 6, 2011 at 7:13 PM, Tim Rogers wrote:
> By the same token, releasing early makes the assumption that significant
> portions of the software in question are believed to operate correctly
> unless stated otherwise. We could absolutely release CoApp “early” in its
> present state, but I
I can understand that, Olaf. If you can hold out for another week or so we
should have everything on the dev side (I think) and much of the client-side
working well enough that common use will be practical. The biggest reason why
CoApp doesn't have that right now is because there have been alm
On Thu, Oct 6, 2011 at 1:38 PM, Charles Strahan wrote:
> The biggest reason why CoApp doesn't have that right now is because there
>> have been almost as many unexpected barriers as there have been days of work
>> on the project.
>
>
> Which reminds me of the symlink issue on Windows (it requires
4 matches
Mail list logo
