My take is simple... sugar should be sold and marketed as a product (like apple) but run as a project (apache, mozilla, launchpad, etc) surely, there must be a middle ground. We can learn from all software, and there is no reason to have to set limits and this point in time? OR are there? In which case, I'd like to know what they are in clear simple terms so we can move towards that? If not, we just have to wait and continue what we are doing...
kind regards, David Van Assche On Mon, Nov 21, 2011 at 6:05 AM, Tabitha Roder <tabi...@tabitha.net.nz>wrote: > On 21 November 2011 09:47, <fors...@ozonline.com.au> wrote: > >> >> I do have a suggestion which is actionable by those on this list: bug >> fixes are more important than new features. >> >> As a tester since mid 2008, I have come across a number of instances > where the stable core activities (things like Write, Memorize, Record) have > been broken in new builds. I would add my +1 to Tony's comment that bug > fixes are more important than new features, and would say (though it is > probably pretty obvious) that we should never ship a build where that core > activity set is broken (core activities were defined once upon a time, I > think there are 6). > > Tabitha > > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > IAEP@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep >
_______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
