[scribus-dev] patches are ready...

[a.l.e]

hi craig,
>  From my recollection of almost if not all patches they were buggy and incomplete. If any have now been fully tested and fixed then please highlight the bugs and final patch files.
>

i would say that every patch added to the bug tracker deserves to be 
rejected or accepted in an explicit and timely manner.

this morning we had a short discussion about this topic on irc and i'd 
like to make the following proposal to make it more self-explanatory, 
what the status of a patch is:

- for trivial patches like http://bugs.scribus.net/view.php?id=11101 ( 
[PATCH] fix for resizing image frame) the way cezary did looks good enough.
- for more complex features like 
http://bugs.scribus.net/view.php?id=11032 ( Patch with marks/footnotes 
feature):
   - there should be a ticket for the feature itself
   - each patch should be uploaded in its own ticket, marked as child of 
the feature request / bug report
   - if the patch is rejected, the ticket gets closed and the 
contributors is asked to create a new ticket with a new patch
   - if the patch has been made from a git branch, the ticket should 
mention the name of the branch and who has tested it

this way it should get easier to track, which patches are waiting to be 
processed (basically: every open ticket that has PATCH in the subject 
should be processed ASAP).


i still would welcome having more than two persons committing code to 
the trunk, but if you were puzzled about which patches were ready, i 
think that such mesures can already help make the situation a bit better.

what do you think?

have a nice evening
a.l.e
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20120928/7ed0d88c/attachment.html>