On Feb 8, 2006, at 17:08, Matt England wrote:
> I manage a significant, private, closed-source software project
> that is considering moving to a completely open-source forum and
> introducing the software and development publicly to an open
> audience on the internet/web.
>
> However, if and when source-code input starts coming from external
> developers, I would like to be able to "stage" the input for
> review, to see what things we want to but in the code repository
> (which is Subversion based), and which things we do not.
>
> How might my website, repo, process, and/or some other mechanisms
> manage this? I assume this is a common problem that is addressed
> in many open-source communities, including Subversion.
>
> Could we exclusively accept patches?
>
> Does Subversion and/or any other tools help automate this "staging"
> process?
Sounds like you want a "feature branch." When a new suggestion comes
in, you can copy your current development code (probably the trunk)
into a branch, make the changes there (by applying a patch provided
by the user, for example, or you could even give that specific user
access to that specific branch), and see how they do. If you hate
them, you delete the branch and forget about it. If you love them,
you merge the changes back into the trunk.
http://svnbook.red-bean.com/en/1.1/ch04s04.html#svn-ch-4-sect-4.4.2
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 8 17:47:08 2006