On Thu, Nov 13, 2008 at 09:58, bruce <bedouglas_at_earthlink.net> wrote:
> hi andy...
>
> regarding your comment, "release management application" for svn.. care to
> recommend any such apps!
It would completely depend upon your environment and what kind of
applications you're developing.
> -----Original Message-----
> From: Andy Levy [mailto:andy.levy_at_gmail.com]
> Sent: Thursday, November 13, 2008 5:21 AM
> To: Ryan Schmidt
> Cc: Derek Gathright; subversion
> Subject: Re: Block a global SVN update and instead require specific
> filenames for update
>
>
> On Thu, Nov 13, 2008 at 00:38, Ryan Schmidt
> <subversion-2008c_at_ryandesign.com> wrote:
>>
>> On Nov 12, 2008, at 17:15, Derek Gathright wrote:
>>
>>> Is there any way to block a user from running just a straight "svn
> update"
>>> on the repo and instead require them to specify specific filenames on the
>>> update?
>>
>> I don't think you can prevent people from updating.
>>
>>> Yes, I know code not ready for production shouldn't be in the repo to
>>> begin with, but sadly that isn't the case and I'm a little freaked out
> about
>>> someone running a global update.
>>
>> Sounds like maybe you need to get the bad code out of your trunk, and move
>> it to a branch.
>
> Not to mention locking down that production environment so that "a
> user" can't update it, and instead a specific release manager (or
> better yet, release-management application) triggers releasing the
> right code to the right place at the right time.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-11-13 16:28:13 CET