Guys,
At long last - Codestriker 1.8 has been released. I've attached the
summary of changes and the CHANGELOG entries for this release, which has
been a long time coming. We are hoping to do more frequent releases from
this point onwards. Grab it from http://codestriker.sf.net.
Enjoy - The Codestriker Team.
From the NEWS:
This major release introduces the capability for automatically and manually
recording configurable software metrics against your code reviews. It is
also possible to generate reports based on these metrics to access the
effectiveness of your code reviews. In addition to MySQL and PostgreSQL,
Codestriker now supports Oracle and SQL-Server via ODBC. There is also the
introduction of Perforce depot integration. Topic properties can now been
modified after a topic has been created. Wildcard searching is now
supported on the search screen for author, reviewer and cc fields. An
audit trail for a topic is now recorded, so that it is possible to see
when a topic was created, who has modified it and when that occurred.
Codestriker now supports execution under IIS, for Win32 deployments,
although Apache can of course be used too.
From the CHANGELOG:
* Initial support for Perforce integration. Can handle topic text
from a Perforce describe command, such as:
"p4 describe -du <changenumber>" or "p4 diff -du".
* Codestriker now works under IIS as well as Apache. Use IPC::Open3
rather than IPC::Run (which doesn't work under IIS) within the
CvsLocal and CvsPserver modules when fetching remote diff data from
CVS. IPC::Run is no longer used.
* A new configuration variable $tmpdir is in codestriker.conf for
unusual setups which can't use the system default temporary
directory for the creation of temporary files. Win32 systems are
the usual culprit.
* The CVS rdiff parser didn't correctly handle new files within the
diff on Win32 platforms.
* Add more win32 example configuration to codestriker.conf.
* Include the relevant DBD modules in the checksetup.pl dependency
list, depending on what database system has been configured.
* Some minor fixes to fully support Win32-based CVS repositories,
including use of the older-style :local:c:\\cvsrep syntax. Also be
more robust in handling directory separators as either forward or
backward slashes, since different versions of CVSNT support this.
Make sure the CVS executable path is quoted, since it will often
contain spaces for Win32 environments.
* Improved useability of messages (when Perl modules are missing) for
Win32 users.
* Now support ODBC and Oracle databases. The Database
creation/upgrade code has been modified so that it is properly
modularised, and so checksetup.pl is far more maintainable. Adding
support for new Databases will now be a snap. The file table had to
be renamed to topicfile, and comment to commentdata to avoid
reserved word clashes in ODBC and Oracle.
* Added in a new topic listener which records all changes to a
comment's state, property changes to a topic and when a topic has
been viewed. Three new database tables have been added to store this
information, which can be accessed from the metrics tab of a topic.
* Added in the ability for the topic's properties to be changed,
including the title, author, bug ids, reviewers, cc, repository,
project, description and state. Updated the topic listeners to now
take the old and new topic objects as arguments.
* Introduction of per-user and per-topic metrics functionality from
Jason Remillard. In the process, the UI has been changed, plus
some general refactoring. It is possible to generate reports
based on these metrics over a collection of topics and time,
to give some indications on the effectiveness of code reviewing.
* The $Codestriker::allow_repository configuration variable is removed
since this boolean value can be derived from the length of the
@valid_repositories list. From Jason Remillard.
* Use tempfile() in Parser.pm to close a potential security hole, from
Jason Remillard.
* The topic search screen has been reworked to contain "What's this?"
links to make the individual search fields clearer. Also, allowed
the use of wildcards with the Author, Reviewer and Cc search fields.
--
Cheers,
David
|
