[sugar] Trac workflow
Mon Jul 21 02:35:10 EDT 2008
Marco Pesenti Gritti wrote:
> I noticed several inconsistencies in the way we deal with tickets,
> which makes working with trac harder than it should be. Here is an
> attempt to describe the workflow from the Sugar point of view:
> 1 Developer looks for the first time at a ticket. If the problem is
> obvious, switch action to code, otherwise to diagnose.
> 2 Developer diagnose the problem, describe it and switch action to code.
> 3 Developer writes a patch, submit it for review per
> http://wiki.sugarlabs.org/go/DevelopmentTeam/CodeReview, switch action
> to review.
> 5 Reviewer gives r+, action is still review.
> 6 Developer check in the patch in git and switch action to "add to build".
We have the 'package' option as well. I guess this is what needs to happen after
checking into git. 'package' is then doing the tarball release and 'add to build'
building in koji maybe? If we do it that detailed we might want to add a 'add to
git' tag as well.
More information about the Sugar-devel