Re: commit-policy

The main reason to present my work in repository is infer from intensive testing requirements. After i significantly polish my code base i'll need as many testers as i can get. Sending by emails or sharing archive with scarab is not good solution. But i can raise svn server in other place, but future merging will be not so easy.

> -----Original Message-----
> From: Völker Ronny [mailto:[email protected]]
> Sent: Friday, March 07, 2008 1:37 PM
> To: [email protected]
> Subject: Re: commit-policy
> 
> Torsten Reuth wrote:
> >I was wondering if using a branch for every new commiter would give
> >somebody a hard time to keep all that branches in sync with the trunk?
> >Shouldn't the changes in the trunk be merged back into the several
> >branches to prevent something sneaking back into the trunk from an
> >outdated branch?
> 
> Rebasing the branch is of course the responsibility of the new committer.
> But it should be fairly easy using svnmerge.py.
> How regularly he does it, is his decision.
> Finally the branch has to be in sync with the trunk every time it gets
> merged back.
> 
> Btw. I would not force anyone to use a branch. Sending patches is still ok
> for me.
> 
> Ronny
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]