For an efficient KDevelop sprint

[Milian Wolff]

Milian Wolff, 30.05.2011:
> Aleix Pol, 27.05.2011:
> > Hi guys!
> > The sprint is approaching and I guess it would be interesting to create a
> > list of things to be treated in the sprint. We'll get a lot of hacking
> > time but also it would be interesting to exchange a little the projects
> > views. Our codebase is quite stable right now and there are some
> > architectural problems that probably should be addressed and I guess
> > that Randa is the best place for that.
> > 
> > My proposal would be to create a small list with things that you want to
> > solve during the meeting so that in the beginning we can discuss about
> > them when appropriate and decide about them.
> > 
> > If anybody has a better idea about how to manage that, it would be
> > interesting to know about it too and if there's someone interested on
> > some problem being solved but is not coming, please tell us so, so that
> > we can think about it :).
> 
> my list so far:
> 
> talking:
> - 4.3 release
> - plasma-based stuff aliex developed last gsoc
> - alpha-style releases of some stuff in quanta

something important that I just remembered:

Unit Tests

I hope to have a FAIL free unit test suite after the sprint. I'll go through 
the code and either XFAIL them or disable unit tests that are unmaintained. 
Any help appreciated.

bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20110531/a2d9984b/attachment.sig>