Release Notes: This maintenance release rolls up a number of fixes for bugs discovered over the past few months.
Release Notes: Problem descriptions can now be added for viewing in the Web interface, and optional printing support is available. The checktestdata syntax has been extended and supports generation of test data. In the judgedaemon, Linux cgroup control of memory limits and networking has been added, which reduces the perceived memory usage by the Java VM. Multiple judgedaemons can now be run on one judgehost machine. Support for four new languages was added: Python 3, Ada, Fortran, Lua, and Scala.
Release Notes: This is a bugfix release rolling up a number of small improvements. The largest impact bugfix concerns an SQL query which could lead to intermittent MySQL locking failures when running with many concurrent users.
Release Notes: This bugfix release rolls up a number of fixes and compatibility improvements.
Release Notes: This release incorporates some minor bugfixes.
Release Notes: A minor bugfix release resolving a crash when compiling on Ubuntu 12.04.
Release Notes: The 3.3 branch delivers some major improvements to DOMjudge. DOMjudge now fully supports submissions consisting of more than one source file. Nearly all aspects of judgehost operation can now be controlled in one place. Optimizations have been made in several places, relevant in large contests. Many smaller improvements and fixes have also been added.
Release Notes: This version fixes multiple minor bugs, and includes minor changes due to the switch from Subversion to Git for source code management.
Release Notes: This release contains a few improvements to the build system only. If you're already running 3.2.0, there's no need to upgrade.
Release Notes: The most notable improvement in 3.2 is the revamped team interface, which now features a "dashboard"-style overview of submissions, clarifications, and scores. Functionality improvements on the jury side include better support for interactive problems, filtering on the scoreboard and submissions, and the ability to delete most data from within the admin interface. On the judgehost side, runguard's setuid root requirement has been replaced with sudo.