workflow adjustments

[Jim Garrison]

I want to suggest the following workflow adjustments:

* Laurent, any time you have a change that you want merged, instead of
pushing it to gitorious, let's instead create (or use an existing)
ticket in trac and upload the patch series there. We can use a tag for
these things "patch-proposed" so I can easily search what needs done.

* If you have a change that is large (e.g. the flashcard editor
overhaul), go ahead and push it to gitorious but have the trac ticket
link to the branch there.

I think this will solve the following things:

* it will get changes necessary for merge out of my inbox. Currently
the things in my inbox representing the work to be done aren't very
useful -- I have an email that says a branch exists, but then I have to
go somewhere else to look at it, and I have to context switch again if I
want to provide feedback.

* currently we end up doing a lot of development and review over private
email. It would be nice to have these threads archived and on the bug
tracker.

Anyway, I think it's worth trying. Let me know if you find that it
creates more work/annoyance for you.

(Btw, it is possible to get a file suitable for uploading to trac by
running "git format-patch --stdout > patch_description.patch")

[Laurent Savaete]

> * Laurent, any time you have a change that you want merged, instead of
> pushing it to gitorious, let's instead create (or use an existing)
> ticket in trac and upload the patch series there.  We can use a tag for
> these things "patch-proposed" so I can easily search what needs done.
>
> * If you have a change that is large (e.g. the flashcard editor
> overhaul), go ahead and push it to gitorious but have the trac ticket
> link to the branch there.

That sounds doable. I'll still push to gitorious, if only to push code
to devbox, and to have a convenient backup in case I fall off my bike
again ;)
But feel free to unsubscribe from gitorious notifications, so you
don't get floods of useless emails. I'll warn you as you suggest
above.

> I think this will solve the following things:
>
> * it will get changes necessary for merge out of my inbox.  Currently
> the things in my inbox representing the work to be done aren't very
> useful -- I have an email that says a branch exists, but then I have to
> go somewhere else to look at it, and I have to context switch again if I
> want to provide feedback.
>
> * currently we end up doing a lot of development and review over private
> email.  It would be nice to have these threads archived and on the bug
> tracker.
>
> Anyway, I think it's worth trying.  Let me know if you find that it
> creates more work/annoyance for you.

I'll give it a try. If that means faster roll out cycles, I'm all for it!