All,
DOMjudge 7.3.2 has been released today; a bugfix release which resolves a
number of issues in our latest stable branch, several of which reported by
our users. Thanks to all those that contributed!
Updated Debian packages are available for this relase which also resolve a
few issues that have been reported in the previous version. Updated Docker
images will follow soon.
Downloads are at: https://www.domjudge.org/download
For the team,
Thijs Kinkhorst
Hi all,
Today DOMjudge 7.3.1 is released, a minor update to our 7.3 release which
includes a number of useful bugfixes.
As usual you can download from https://domjudge.org/download.
Updated Debian packages are available in our repository. New Docker images
will follow tomorrow.
On behalf of the team,
Thijs
Hi all,
Today we've released DOMjudge 7.3.0.
This new feature release bundles up a number of newly developed features
and improvements that were made in the past months. For details see:
https://github.com/DOMjudge/domjudge/blob/7.3/ChangeLog
Updated Docker images are available, and starting from this release we've
resumed to ship Debian packages from the repository documented on our
website. Please head to https://www.domjudge.org/download for instructions
or to download the new release.
…
[View More]Thanks to all who reported issues and provided pull requests. It's really
great to see contributions from so many different people.
On behalf of the team,
Thijs Kinkhorst
[View Less]
Hi all,
Today we've released bugfix updates of DOMjudge 7.2 and 7.1.
These fix a number of bugs discovered in the past months. Thanks to all
the users reporting them or even providing a suggested fix. We recommend
upgrading to these releases, for the most flawless DOMjudge experience.
They can be downloaded from https://www.domjudge.org/download
Updated Docker images are also available.
(There are no Debian packages for these release branches. We expect that
Debian packages will be offered …
[View More]again starting with the 7.3 branch which
is currently under development.)
On behalf of the team,
Thijs Kinkhorst
[View Less]
Hello all,
Tomorrow, we are running a hackathon to work on DOMjudge. This was initially planned in real life, but due to Covid-19 we turned it into an online event. We'll start around 8am UTC and will coordinate on DOMjudge slack channel #hackathon and through a video conference call at https://meet.jit.si/DOMjudge_hackathon
Anyone interested is welcome to join either the slack channel and/or the video conference!
On behalf of the DOMjudge developers,
Jaap
Hi all,
Today we’ve released DOMjudge 7.0.5. This is a rollup bugfix release for the 7.0 series with the following fixes:
- Fix output limit check when uploading new testcases (thanks Irfan Sofyana Putra).
- API: only output test data count for jury members.
- Do not show First To Solve when the problem has not been solved w.r.t. the restrictions.
- Fix balloon page when we do not have award info.
- Clarify documentation.
It can be downloaded from https://www.domjudge.org/releases/
This …
[View More]also marks the end of life of version 7.0 (and of all previous release series).If you are running any previous version you are recommended to upgrade to one of the currently supported versions 7.1 or 7.2.
On behalf of the DOMjudge team,
Jaap Eldering
[View Less]
Hi all,
Today we’ve released DOMjudge 7.2.0, which brings new features
and fixes some bugs. The most notable new features include:
- Rewrote documentation into a completely new DOMjudge Manual.
- Improve performance using multiple fixes.
- Improve submission and judging run display in jury interface.
- Added some endpoints to the API.
- Use modern compiler options in internal build scripts.
- Update default configuration values to modern system limits.
- Add simple script to …
[View More]import a whole contest from a CLICS compatible
ccsconfig directory.
- Add a command to merge scoreboards from multiple ICPC Contest API
endpoints (#632, thanks Ragnar Groot Koerkamp).
For the full changelog, see https://github.com/DOMjudge/domjudge/blob/7.2/ChangeLog
We would like to thank everyone who contributed to this release by creating issues,
pull requests or feature requests.
We have also released 7.1.2 with some bugfixes.
Downloads are at https://domjudge.org/download
Updated Docker images are also available Docker Hub. APT packages
and live images will follow soon.
On behalf of the DOMjudge team,
Nicky Gerritsen
[View Less]
Hi all,
Today we've released DOMjudge 7.1.1, which contains a number of fixes for
problems discovered since the last release.
It can be downloaded from
https://www.domjudge.org/download
Docker and live images, as well as updated Debian packages,
will follow soon.
Thanks go to the several DOMjudge users that reported the bugs.
On behalf of the team,
Nicky
Hi all,
Today we’ve released DOMjudge 7.1.0, which brings new features
and fixes some bugs. The most notable new features include:
- Judgedaemons will now keep retrying when an endpoint is unavailable.
- Support for shadowing another CCS.
- Allow for non-public contests with all teams and for public contest with
only specific teams
- Allow to add a whole team category to a contest.
- Use a new way to migrate the database.
- Allow to limit files passed to compilers.
- Add configuration …
[View More]option for print command.
- Re-add support for downloading statistics SVG’s.
For the full changelog, see https://github.com/DOMjudge/domjudge/blob/7.1/ChangeLog
We would like to thank everyone who contributed to this release by creating issues,
pull requests or feature requests.
We have also released 7.0.4 with some bugfixes.
Downloads are at https://domjudge.org/download
Updated Docker images are also available Docker Hub. APT packages
and live images will follow soon.
On behalf of the DOMjudge team,
Nicky Gerritsen
[View Less]
Hi all,
Today we've released DOMjudge 7.0.2, which contains a number of fixes for
problems discovered since the last release.
It can be downloaded from https://www.domjudge.org/download
Updated Debian packages are also available from our APT archive. Docker
and live images will follow soon.
Thanks go to the several DOMjudge users that reported the bugs.
On behalf of the team,
Thijs