JCR 0.6.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News JCR 0.6.4 (Default branch)
# 1  
Old 08-24-2008
JCR 0.6.4 (Default branch)

Image JCR is a Web application for performing and managing formal code reviews. Although it has some special logic for reviewing Java projects, it can be used for reviews of any type of source code. JCR manages all stages of the review process (initial project setup, individual review, joint review meeting, post-review tidy-up), but it's mainly there to show diff views of files that have changed and to allow comments to be made on any line of any file marked for review. License: GNU General Public License (GPL) Changes:
This release includes the ability to view file diffs as side-by-side. The project status report now provides an indication of the review activity for each file, so you can see files that may not have been reviewed. There are other minor usability enhancements. The version of the Pylons application framework installed has been restricted due to incompatible API changes in a new version. There is a status report update.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME
archpath - output arch (tla/Bazaar) archive names, with support for branches SYNOPSIS
archpath archpath branch archpath branch--version DESCRIPTION
archpath is intended to be run in an arch (tla or Bazaar) working copy. In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working copy. If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current archive and category and with the same version as the current working copy. This is useful for branching. For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a com- mand like this: baz branch $(archpath) $(archpath new-feature) Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this: baz branch $(archpath) $(archpath releases--1.0) That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result. AUTHOR
archpath was written by Colin Watson <cjwatson@debian.org>. Like archpath, this manual page is released under the GNU General Public License, version 2 or later. DEBIAN
Debian Utilities ARCHPATH(1)