[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] General Subclipse Usage Question

From: DM Smith <dmsmith555_at_yahoo.com>
Date: 2006-02-16 20:13:52 CET

etornick wrote:
> We are thinking about using subclipse for a large project. This project will
> have many developers, and some will be coming on board as newbies.
> Additionally we are thinking of having a release manager be a coordinator of
> the creation of the branches and tags.
> For the most part, the developers will be working off the trunk until we
> start gettting into more formal release procedures, then people might be
> assigned to work on a branch for a specific maintenance release etc...
> What concerns me is that it seems incredibly easy to go into the repository
> view and select a folder (like the branches folder - (using the suggested
> subversion folder layouts of branches - tags - trunk....)) and right click
> and delete!!! You could blow away 50 branches this way!

Another way is to have a small group of committers that have write (thus
delete) privs.
Everyone else has read privs and they submit patches to the committers.

In this scenario, the committers would be trusted to do the right thing.

> I experimented with this a bit and it really did the delete from the
> "eclipse perspective". The project in another eclipse workspace seemed to be
> orphaned because when I tried a team->synchronize it said there was nothing
> to synchronize with.
> I figured there must be a way to control this so that certain people could
> be restricted to doing certain operations and it seems like the "hooks" were
> the only way.
> Any ideas/thoughts on how to deal with this issue would be greatly
> appreciated.
> Thanks,
> Ed

To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 16 20:14:22 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.