Codestriker 1.7.1 released

A lot of new significant features are included in this release, including:

* The notion of "projects" has been integrated. Now every topic in
the system is associated with a single project. There are now
screens for creating new projects, and modifying their
names/descriptions. It is now possible to perform topic searches
and to limit it within specific projects. This has been added in to
support deployments where there is a large number of users working
on different projects. The create topic and view topic screens have
been modified accordingly.

Note there is a new configuration option in codestriker.conf called
$allow_projects. If this is set to non-zero, then the project
management screens will be accessible, otherwise they can't be
accessed. This can be convenient for those deployments which have
set their project data, and don't want it modified.

* Pserver repository type has been added, so that code reviews against
remote CVS repositories can be linked using :pserver. See the
codestriker.conf file for more information.

* When creating a review, instead of uploading a diff file, a start
tag, end tag and module name can be given as input. Codestriker
will fetch the review text and initialise the topic appropriately.
This better suited some development processes out there, where
separate branches were used for development, which needed to be
reviewed before collapsing to a trunk. These options are only
displayed if repositories are enabled ($allow_repositories == 1) in

* Support for parsing output from "cvs rdiff -uN -r TAG1 -r TAG2
module". This was required to support the "TAG input" method above.

* Make sure that topic text that has DOS line endings \r\n are
correctly parsed.

* Fixed a bug where searches over comment data wasn't returning
correct results.

* Minor changes to checksetup - make sure the template directory is
cleaned out to ensure the templates are regenerated when performing
an upgrade.

* Changed codestriker.conf to use single quotes rather than double, so
that there are no Perl escaping issues.

Posted by David Sitsky 2003-04-17

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks