Sander Roobol <phy@wanadoo.nl> writes:
> Ok, will do that. I hoped that posting this list would have enough
> effect, but apparently, it hasn't.
:-)
Sorry, I maybe should have explained a bit better. The issue isn't
about prodding or motivation -- it's more a question of "What's the
most convenient organizational structure for tracking patches?" It
happens that the issue tracker gives us exactly what we need. That's
why I mentioned it in the original patch manager post:
> When you see one, flag it and keep an eye on that thread. If no
> resolution happens within a few days, then post asking what's up.
> If no one can take it right then, then file it as a PATCH issue
> (we'll figure out the milestone based on the patch). Even that
> much would smooth away a lot of the administrative burden, and
> give developers an easy overview of exactly what's out there.
Otherwise, what we'll have is a bunch of people posting followups to
your "[PATCH][PATCH][PATCH]" email, quoting different parts of it and
saying "I'll take this one" or "I'll take that one". It would be
impossible to keep track of who's got what. Not impossible for you,
of course, since you're keeping personal records, but impossible for
anyone who isn't keeping such records, i.e., anyone who isn't doing an
amount of work equivalent to being patch manager :-).
So the point of using the issue tracker is to take the work you've
done and "distribute" it to everyone.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 11 19:56:57 2003