[Codestriker-user] Codestriker 1.8.4 released
Brought to you by:
sits
|
From: David S. <si...@us...> - 2004-10-05 23:45:15
|
Hi everyone, Codestriker 1.8.4 has just been released. Its is available from http://codestriker.sourceforge.net, in the usual place. I've appended the CHANGELOG to this email. Cheers, The Codestriker Team. Version 1.8.4 * The topic properties page now displays the start tag, end tag and module parameters if they were used when the topic was created. Contribution by Robert Hudson <cod...@go...>. * The repository property has been changed to be a read-only property in the topic properties page, from Robert Hudson. * The repository selection drop-down is only selected if there is more than one repository configured in the system, from Robert Hudson. * If a topic is not in open state, then the "topic information" and "topic comments" pages are modified to readonly, and adding new comments is disabled. From Robert Hudson. * In the table of contents, display the total number of lines added and removed for each file. This gives the reviewer a quick idea where the major changes in the review are. From Robert Hudson. * There is a new configuration option @project_states which controls whether a project can have its state changed to 'Closed', which prevents new topics being created within it, and the state 'Deleted', which will delete the project and all its member topics. Both of these new states are optional, and are not available by default. From Robert Hudson. * When sending emails involving more than one CC recipient, the email sending may fail because a space wasn't put after each comma. * Created the CodestrikerClient module in bin which can create a new topic non-interactively. The intention is for this module to be used from scripts that need to create new topics, for example, from a CVS post-commit script. * Modified custom CVS post-commit scripts so that a Codestriker topic is created for each CVS commit, along with a sent email. The commit_prep.pl and log_accum.pl are located in the bin directory, and need to be copied into your CVSROOT area, with a line like the following in your commitinfo file: DEFAULT $CVSROOT/CVSROOT/commit_prep.pl -r and a line like the following in your loginfo file: DEFAULT $CVSROOT/CVSROOT/log_accum.pl %s The log_accum.pl file needs to have some configuration variables set at the start of the script to reflect your site. Note the first line of the log message will be used as the topic title. The entire log message is used as the topic description. Any strings of the form "Bug nnn" in the log message will be taken as a reference to a bug id, and will be used in the topic's bugid field. * Added an optional show_on_mainpage attribute to the comment metrics configuration, which specifies which comment metric counts will appear on the topic list page. From Jason Remillard. * Reviewers who haven't viewed a topic will have their names surrounded by parenthesis in the topic list page. From Jason Remillard. * Fixed a number of taint-mode problems when using Perl 5.8. * Fixed the "Attempt to bless into a reference" error when using Bugzilla integration and Perl 5.8. * Migrated the MySQL datetime type from TIMESTAMP to DATETIME, as it should have always been. From Jason Remillard. |