> We already have many options that CVS does not have, and
> would certainly expect to since SVN has options that CVS does
> not have. But we also have many features, such as bug
> tracking integration that CVS does not have. We are not
> trying to limit ourselves based on CVS, but we certainly try
> to learn from them. Also, since we have proposed moving
> Subclipse to Eclipse, I do see benefit in presenting a
> consistent UI between the plugins. There is currently a
> common History view, I'd like to see a common Repository view
> added eventually. Some of our dialogs are at least similar
> if not identical.
So the answer could be:
- If it's a change introduced by SVN (10 points)
- If it's a huge improvement in usability (10 points)
- If it's a small improvement in usability (1 point)
- If some other people like (1 point)
- If a lot (> 10) of people like (2 points)
- If you like (10 points)
- If you don't like (-10 points)
- If it makes Subclipse more divergent from CVS plugin (-10 points)
- If it gives some trouble to implement and nobody submits a patch (-10
points)
- If it gives some trouble to implement and somebody submits a patch (-1
point, for having to check it)
-> To implement, points > 0.
And therefore, a small improvement that makes Subclipse slightly more
divergent from CVS plugin will always be dropped. Right?
Thank you,
Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Oct 16 23:08:11 2006