On Mon, Jul 22, 2013 at 3:16 PM, Trevor Davel (Twylite) <twyl...@crypt.co.za > wrote:
> Hi, > > > On 2013/07/21 12:54 PM, Stephan Beal wrote: > >> To help bootstrap the process of figuring out what Fossil v2 might look >> like i have started writing down ideas in a public Google Doc: >> >> https://docs.google.com/**document/d/12g0s5A2TPX7-** >> y47Nsw235rvsjcuh49TnHfMDB4ASvl**o/view<https://docs.google.com/document/d/12g0s5A2TPX7-y47Nsw235rvsjcuh49TnHfMDB4ASvlo/view> >> > > One feature I would love to see in Fossil v2 (or v1) is support for > tracking code reviews. This would cover finding commits that require > review, flagging the commit once the review has been completed, and > reporting on what has been reviewed (and by whom). > > One approach would be to have non-propagating review tags on commits, > specifically including the ability to search for unreviewed commits by > branch. > Speaking of: being able to tag non-branches (e.g. tagging individual wiki pages or files) is something i'd like to add/see added to v2. > An alternative realisation would be to automatically create "Review" > tickets for any commit on a branch that has a specific propagating tag > indicating that review is required. > That sounds like a fairly straightforward implementation which could fit in the current architecture. All added to the list... -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
