<div class="gmail_quote">On Sun, Oct 25, 2009 at 2:07 PM, Boudewijn Rempt <span dir="ltr"><<a href="mailto:boud@valdyas.org">boud@valdyas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Sunday 25 October 2009, Boudewijn Rempt wrote:<br>
<br>
</div>Oh, and for trunk I'd like to propose the following, since we don't have a<br>
nice gitorious environment yet with staging tree and all that:<br>
<br>
* plugins can always be committed, no matter what the state.<br>
* bug fixes need to have a bugzilla number, create a bug yourself if needed,<br>
they need to be created for 2.1, reviewed, and then applied to 2.1 and trunk<br>
* trunk refactorings need to be proposed on the mailing list, where people<br>
participating in a discussion can ask for the patch to be reviewed first.<br>
<br>
Anything I've forgotten?<br></blockquote></div><br>I think we shoud have something like the Kexi TODO <a href="http://wiki.koffice.org/index.php?title=Kexi/TODOs">http://wiki.koffice.org/index.php?title=Kexi/TODOs</a><br>
So we say Krita 2.2 aims for performance and blender movie usage.<br><br>We should analyse what needed for this and then list all planned features, refactorings etc. there and assign prioritys to them.<br>That way I hope we could be a better overview what everybody is working on.<br>