Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

custom properties for code review/todo items #63

Open
GoogleCodeExporter opened this issue Sep 22, 2015 · 4 comments
Open

custom properties for code review/todo items #63

GoogleCodeExporter opened this issue Sep 22, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

Feedback from Subversion Live 2011 in San Jose:
(just a suggestion, this needs a lot of discussions first)

quote from email:

Let me paint a picture:

Your organzation believes in code review.  ie a senior programmer looks a 
junior programmers code and after he reviews it sets the svn property 
"codereview" to passed or failed.  Obviously the code could move in and out of 
these states as it evolves.

The fact that the latest revision of code is marked "codereview:failed" would 
prompth the person responsible for the code to fix it up to coding standards. 
(comments, variable names, indentation etc)
The reviewer can obviously make comments about what is wrong in the Log 
Messages when he/she checks in the code with a changed property.

Where this breaks down is:
1.How does anyone "easily" find out which files (or versions of files) have 
this propert set?
2. It would be nice to be able to limit the property input to the values "pass 
and fail", and it would be even better if these values could be selected.
3. It would be cool if selectively, a user could have a column in the "log 
messages" and "repo-browser" set to a specific property.(like Bug-ID's)
4. Some sort of report would also be nice.

Just passing on ideas.

Original issue reported on code.google.com by tortoisesvn on 3 Feb 2011 at 7:39

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant