Merged requested to merge 575-consecutive-slot-filling-mode into development
What does this mr do?
Mode: 100/0. As seen in this SS, once the slot starts the next one opens:
After the first slot completely closes (current time passes closing time), the next one opens up:
Mode: 50/0. Next slot opens once a given slot is pseudo full, (threshold is 50%) in this case.
Both preceding slots are pseudo-full, and therefore the 3rd slot opens.
Mode: 100/2. If the second parameter is not 0, it basically acts as a sliding window
After a few people enque it looks like this:
Note that if the last slot in the sliding window is full, it still works as intended
Note to Reviewers
I am open to suggestions on how to phrase the parameters for the end-users. Currently it is horrible.
Does this MR meet the acceptance criteria?
I have added a changelog entry to reflect the significant changes I made.
Tests were created to test the feature.
I have updated the documentation accordingly.
I adhere to the style guide.
Closes #575 (closed)