Baseline creation should be a background task / long-running-task,
Made of sequential transactions of no more than 25s (as per ),
Also, ideally:
Baselines should have a status: "PLANNED", "IN CREATION", "DONE".
Since there is a status, add a history field.
Design 1 more status for our concept of parallel branches / fork / editable baselines.
Design whether we should lock baselines or not, to allow "extending" a baseline.
Related to and .
Important note
Feature removal 1: Dependencies
Before freezing a baseline, it used to be possible to see requirements and add them to the baseline.
Unfortunately, as soon as the baseline is larger than 1 page of search results (600 by default), it is impossible to make this calculation accurately and without altering performance (We would have to load all requirements from the database and mix-and-match their dependencies).
Rather than misleading the users into thinking the results are accurate, we are removing this feature:
In the initial baselines, dependencies will be suggested but there won’t be a button to add them automatically,
In the “refreeze” process, dependencies will not be suggested.
Feature removal 2: Summary before building a baseline
Before a freeze, we used to give the number of pages. We won’t do that anymore, because it takes too long to calculate. We’ll still provide the expected number of requirements in the future baseline.
Before a refreeze, we used to give a detail account of the number of requirements added/overridden/removed from the previous baseline. We don’t do that anymore, because it takes too long to calculate.
Feature removal 3: Baseline page titles
When a baseline page (the page where a baseline is summarized) was renamed, it used to rename the baseline synchronously. We have removed this feature, notably because it was a drain on the performance, and baseline pages are not so important anymore.
Please rename baselines using the baseline list, and the page will be updated:
Feature removal 4: Changing the search query of a baseline using the macro
It was possible to modify the search query of the baseline, on the baseline page, up until the requirements were frozen. In the new system:
If there is already a “baseline” record for this page, it already contains the search query. We won’t update it when you click “Freeze requirements”.
If there isn’t already a “baseline” record, the button will read “Prepare baseline”. Clicking on it will create the record and save the search query, but not freeze the requirements.
Feature changes
All forms related to baselining have changed, to make the baselines a background task:
The instant baselines, in the byline of the pages,
Baseline creation should be a background task / long-running-task,
Made of sequential transactions of no more than 25s (as per ),
Also, ideally:
Baselines should have a status: "PLANNED", "IN CREATION", "DONE".
Since there is a status, add a history field.
Design 1 more status for our concept of parallel branches / fork / editable baselines.
Design whether we should lock baselines or not, to allow "extending" a baseline.
Related to and .
Important note
Feature removal 1: Dependencies
Before freezing a baseline, it used to be possible to see requirements and add them to the baseline.
Unfortunately, as soon as the baseline is larger than 1 page of search results (600 by default), it is impossible to make this calculation accurately and without altering performance (We would have to load all requirements from the database and mix-and-match their dependencies).
Rather than misleading the users into thinking the results are accurate, we are removing this feature:
In the initial baselines, dependencies will be suggested but there won’t be a button to add them automatically,
In the “refreeze” process, dependencies will not be suggested.
Feature removal 2: Summary before building a baseline
Before a freeze, we used to give the number of pages. We won’t do that anymore, because it takes too long to calculate. We’ll still provide the expected number of requirements in the future baseline.
Before a refreeze, we used to give a detail account of the number of requirements added/overridden/removed from the previous baseline. We don’t do that anymore, because it takes too long to calculate.
Feature removal 3: Baseline page titles
When a baseline page (the page where a baseline is summarized) was renamed, it used to rename the baseline synchronously. We have removed this feature, notably because it was a drain on the performance, and baseline pages are not so important anymore.
Please rename baselines using the baseline list, and the page will be updated:
Feature removal 4: Changing the search query of a baseline using the macro
It was possible to modify the search query of the baseline, on the baseline page, up until the requirements were frozen. In the new system:
If there is already a “baseline” record for this page, it already contains the search query. We won’t update it when you click “Freeze requirements”.
If there isn’t already a “baseline” record, the button will read “Prepare baseline”. Clicking on it will create the record and save the search query, but not freeze the requirements.
Feature changes
All forms related to baselining have changed, to make the baselines a background task:
The instant baselines, in the byline of the pages,
The baseline wizard,
The ability to baseline on a baseline page.