Skip to content

Commit

Permalink
auto: deploy new website
Browse files Browse the repository at this point in the history
  • Loading branch information
@nipreps-bot
nipreps-bot committed Dec 14, 2024
1 parent 8276564 commit 7ec3952
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions devs/releases/index.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1068,10 +1068,10 @@ <h3 id="bug-fix-releases">Bug-fix releases<a class="headerlink" href="#bug-fix-r
<ol>
<li><strong>Resolving one or more bugs.</strong> These mostly include failures of <em>fMRIPrep</em> to complete or producing invalid derivatives (e.g., a NIfTI file of all zeroes).</li>
<li><strong>Derivatives compatibility.</strong> If a subject may be successfully run on 20.0.n, then the imaging derivatives should be identical if rerun with 20.0.(n+1), modulo rounding errors and the effects of nondeterministic algorithms. The changes between successful runs of 20.0.n and 20.0.(n+1) should not be larger than the changes between two successful runs of 20.0.n. Cosmetic changes to reports are acceptable, while differing fields of view or data types in a NIfTI file would not be.</li>
<li><strong>API compatibility.</strong> Workflow-generating functions, workflow input- and outputnode fields must not change. As an end-user application, this may seem overly strict, but the odds of introducing a bug are much higher in these cases.</li>
<li><strong>API compatibility.</strong> Workflow-generating functions, workflow <code>inputnode</code> and <code>outputnode</code> fields must not change. As an end-user application, this may seem overly strict, but the odds of introducing a bug are much higher in these cases.</li>
<li><strong>User interface compatibility.</strong> Substantial changes to <em>fMRIPrep</em> command line must not happen (e.g., the addition of a new, relevant flag).</li>
</ol>
<p>Note that not all bugs can be fixed in a way that satisfies all three of these criteria without significant effort. A developer may determine that the bug will be fixed in the next feature release.</p>
<p>Note that not all bugs can be fixed in a way that satisfies all four of these criteria without significant effort. A developer may determine that the bug will be fixed in the next feature release.</p>
<p>Additional acceptable changes within a minor release series:</p>
<ol>
<li><strong>Improved tests.</strong> These often come along with bug fixes, but they can be free-standing improvements to the code base.</li>
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json
View file

Large diffs are not rendered by default.

0 comments on commit 7ec3952

Please sign in to comment.