@eisenman yes, should be sufficient
only one case per task covered in bootstrap() now see T28202

bootstrap() now gives error if all tasks only contain 1 test case and a message if some tasks contain only 1 test case (tasks with 1 test case are excluded from bootstrapping)
test-bootstrap.R contains tests. @eisenman could you please check test

Additional comment: the missing library doesn't prevent the Workbench from starting, but some/all DICOM functionality is missing which can be confusing

Ok, I just re-checked: Ubuntu 20.04 still has librwrap installed , so installer works. For Fedora there is no workaround , so either

The unit tests can be found here: feature/T28193-UnitTestsMoreTasksThanAlgorithms

I will extend the unit tests to show that this issue is solved.

In T28000#218184, @kalali wrote:

Is there something we should take care of in the future when writing commit messages or writing differential summaries? Or is this something we can not avoid and has to be done when combining everything for the regular changelog?

In T28000#218153, @kislinsk wrote:

I noticed that simply merging all the changelogs section-wise doesn't work out very well and generates an overwhelming document probably noone is going to read. I propose the following for the release changelog:

• Merge the thirdparty dependency update table (simple)
• Focus on feature and bugfix oneliners and reference the original changelog if there is more related information
• Roughly sort them by importance/shinyness
• List references to original changelogs with API-breaking changes but explicitly mark the "big ones" that have migration hints/guides

TFDA mvp0 code has been moved to a feature branch under kaapana-internal

The change log proposal sounds reasonable to me.

I noticed that simply merging all the changelogs section-wise doesn't work out very well and generates an overwhelming document probably noone is going to read. I propose the following for the release changelog:

Pushed new branch to rMITK MITK: release/T28000-v2021.01.

Pushed new branch to rMPT MITK-ProjectTemplate: release/T28000-v2021.01.

task names ( names(x$matlist) ) had been used for facet titles instead of algorithm names ( stored in "ordering").

What exactly is the error? What are the steps to reproduce this? Runtime error or wrong content in report?

Deleted branch from rMITK MITK: release/T28197-2021-Week-04.

Pushed new branch to rMITK MITK: release/T28197-2021-Week-04.

Fixed with D450

Fixed with T28118 (D450)