much more frequent worker cycles

[rlaemmel]

Not assigning this one. Not expecting that anyone will do this shortly. We can discuss this anyway at the next scrum.

cc @kevin-klein @hartenfels @martinleinberger

There are many good reasons why all worker-derived resources should be up-to-date. One is the emerging intellisense features for the wiki. That is, that page names are listed when editing metadata or links.

There are presumably these options for having more frequent work cycles.

1. We just use the current worker cycle and run it more often. This would work if a) most modules are pretty incremental with regard to 101repo changes, where possible; b) all the remaining modules are either very cheap and/or really needed for scenarios that ask for frequent cycles.
2. We define a shorter list of modules for the more frequent runs and run the fuller list only more often.

As I said, let's discuss at some point soon.

[kevin-klein]

I prepared a small demo and a small presentation, i would like to present this during the meeting tomorrow (1.6.). It is about a more message based approach instead of nightly builds.

[hartenfels]

@kevin-klein Can you maybe put the presentation somewhere? I can't be attending since there's a tutorial in the same time slot.