On using svn for submitting patches

I'm trying to understand how SVN can be used to prepare patches
against open development projects, e.g. svn. The conundrum is as
follows.

  1) Public development proceeds along a path. There are asynchronous
     updates to the main line of code.
  2) Local development proceeds on several fronts. We may be fixing
     bugs as well as developing new features.
  3) Patches submitted for inclusion in the public archive may require
     changes before being accepted.
  4) Pending patches may be necessary for development on several
     fronts. For example, a bug fix may found and submitted while
     working on a new feature and before that feature is ready for
     submission.

My first approximation is to let the trunk reflect the published
development process with a branch for each line of development. For
example, a bug fix would be pursued on a branch of its own. Likewise,
new features are developed in a branch per submittable chunk.

The questions are

  Is this a reasonable method for developing 'patches'?
  Is there something better?

Cheers.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 10 01:28:53 2003