RE: Parseable tracking of code contributions.

>>Let's use a parseable format in log messages,
>>for recording code contributions, analysis,
>>and review. The format would look something
>>like this:

A potentially stupid idea: How about using Subversion
for patch management?

Create a branch area where each committer-wannabe can
apply their patches (alternatively, the patches
themselves in unidiff format)

Each committer-wannabe would get access to their own
branch for their patches. They would perform and test
the merge of the patch themselves. If they do great
work over time, they get trunk access :-)

I.e: ...\svn\patches\<committer-wannabe-username>\...

When the reviewer is happy about the patch, he merges
it with trunk. If not, the committer-wannabe makes the
requested changes and recommits to his private branch,
and the review process goes on.

This would give you a great overview of who did what
and when, and you wouldn't need to spend time dealing
with ill-formatted patches, etc. The patches
themselves would be versioned too :-)

Reviewers would get mail notifications about patches
(using the usual hooks) - dev@ would also get
notifications about submitted patches, with a link to
it.

There could even be hooks that analyzed the committed
patch to see if it adhered to coding standards and so
on.

Oh well.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 14 12:40:30 2005