Kobayashi Noritada wrote:
> Hi,
>
> I propose /branches/svn-ruby or something so that kou can use it.
> I think this may be a bold proposal, but makes developing and logging
> transparent, and also makes reviewing smooth.
>
> Because I'm interested in it, I am reviewing it bit by bit.
> However, bindings are developed daily, patches getting larger and larger,
> and logs changing day by day.
> Also, I am not a full committer and do not have a privilege to approve
> committing it even if I finish reviewing :-)
> So, if it is not appropriate for kou to use /trunk,
> how about creating /branches/svn-ruby or something and giving kou a commit
> access to it until diffs of /trunk and the branch are completely reviewed
> by someone?
> If kou can use /branches/svn-ruby, everyone can know developing status and
> its log, and review it.
> Also, he can merge parts of binding codes to /trunk, if approved.
>
> How do you like this idea?
+1, getting this into a branch would reduce the effort required for
people to test it out, which would make it easier to review, etc.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Feb 13 18:04:57 2005