thron7-2 wrote > > > 1. Our workflow is driven by bugs/issues. Nothing really happens without > a bug. We can discuss and analyse a lot on the mailing list. But without > a bug you will hardly see any form of implementation, be that framework > classes, documentation or project infrastructure. > [...] > >
Does this in other words mean that qooxdoo development (by the core team) has basically come to a standstill as long as we don't file any bugs? -- View this message in context: http://qooxdoo.678.n2.nabble.com/the-contrib-site-tp7580681p7580778.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
