<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Evaluation on Deevnet IoTaaS</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/</link><description>Recent content in Evaluation on Deevnet IoTaaS</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/index.xml" rel="self" type="application/rss+xml"/><item><title>Hardware Evaluation</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/hardware-evaluation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/hardware-evaluation/</guid><description>&lt;h1 id="hardware-evaluation">
 Hardware Evaluation
 &lt;a class="anchor" href="#hardware-evaluation">#&lt;/a>
&lt;/h1>
&lt;p>How a model of hardware is evaluated for a role. For a model in service, the record is its own page
under 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/hardware/">Hardware&lt;/a>. For a candidate, it is under

 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/evaluations/hardware/">Evaluations → Hardware&lt;/a> until it is selected.&lt;/p>
&lt;hr>
&lt;h2 id="what-is-evaluated">
 What is evaluated
 &lt;a class="anchor" href="#what-is-evaluated">#&lt;/a>
&lt;/h2>
&lt;p>A &lt;strong>model at a hardware revision, for a role&lt;/strong>. The same model in a different role, or at a different
hardware revision, is a separate evaluation. Hardware revisions do change what a board carries,
such as the NIC chipset.&lt;/p></description></item><item><title>Software Evaluation</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/software-evaluation/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/software-evaluation/</guid><description>&lt;h1 id="software-evaluation">
 Software Evaluation
 &lt;a class="anchor" href="#software-evaluation">#&lt;/a>
&lt;/h1>
&lt;p>How a release line of a product is evaluated for a role. The records are under

 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/evaluations/software/">Evaluations → Software&lt;/a>.&lt;/p>
&lt;hr>
&lt;h2 id="what-is-evaluated">
 What is evaluated
 &lt;a class="anchor" href="#what-is-evaluated">#&lt;/a>
&lt;/h2>
&lt;p>A &lt;strong>release line of a product, for a role&lt;/strong>: OPNsense 26.7 as the core router, Proxmox VE 9 as a
hypervisor, Grafana 13 as the tenant dashboards. Device firmware is software, and is evaluated the
same way.&lt;/p>
&lt;p>&lt;strong>A line, not a version.&lt;/strong> Patch releases inherit the line&amp;rsquo;s approval. Before a patch is applied,
its release notes are read. If they change something a criterion depends on, the patch is
re-checked against that criterion, and the result is a dated addendum on the line&amp;rsquo;s record.
A new line is a new revision.&lt;/p></description></item><item><title>Evaluation Record Template</title><link>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/evaluation-record-template/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/evaluation/evaluation-record-template/</guid><description>&lt;h1 id="evaluation-record-template">
 Evaluation Record Template
 &lt;a class="anchor" href="#evaluation-record-template">#&lt;/a>
&lt;/h1>
&lt;p>The shape of an evaluation record: one &lt;strong>item page&lt;/strong> per model or product, and one &lt;strong>revision page&lt;/strong>
per evaluation beneath it. Copy the skeletons below.&lt;/p>
&lt;hr>
&lt;h2 id="where-it-goes">
 Where it goes
 &lt;a class="anchor" href="#where-it-goes">#&lt;/a>
&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>&lt;/th>
 &lt;th>Hardware&lt;/th>
 &lt;th>Software&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Item&lt;/strong>&lt;/td>
 &lt;td>In service: the model&amp;rsquo;s page, &lt;code>content/docs/platforms/hardware/&amp;lt;group&amp;gt;/&amp;lt;model&amp;gt;/_index.md&lt;/code>. A candidate: &lt;code>content/docs/platforms/evaluations/hardware/&amp;lt;model&amp;gt;/_index.md&lt;/code>&lt;/td>
 &lt;td>&lt;code>content/docs/platforms/evaluations/software/&amp;lt;layer&amp;gt;/&amp;lt;product&amp;gt;/_index.md&lt;/code>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Revision&lt;/strong>&lt;/td>
 &lt;td>&lt;code>…/&amp;lt;model&amp;gt;/&amp;lt;YYYY-MM&amp;gt;-hw-&amp;lt;revision&amp;gt;.md&lt;/code>, e.g. &lt;code>2026-10-hw-1-20.md&lt;/code>&lt;/td>
 &lt;td>&lt;code>…/&amp;lt;product&amp;gt;/&amp;lt;line&amp;gt;.md&lt;/code>, e.g. &lt;code>26-7.md&lt;/code>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Layer&lt;/strong>&lt;/td>
 &lt;td>&lt;code>network&lt;/code> or &lt;code>compute&lt;/code>, as on 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/hardware/">Hardware&lt;/a>&lt;/td>
 &lt;td>&lt;code>network&lt;/code>, &lt;code>management-plane&lt;/code> or &lt;code>tenant-compute&lt;/code>, as on 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/">Implementation &amp;amp; Tooling&lt;/a>, or &lt;code>tooling&lt;/code> for build and automation tools&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Item title&lt;/strong>&lt;/td>
 &lt;td>The model, e.g. &amp;ldquo;TP-Link SG2218&amp;rdquo;&lt;/td>
 &lt;td>The product, e.g. &amp;ldquo;OPNsense&amp;rdquo;&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Revision title&lt;/strong>&lt;/td>
 &lt;td>&amp;ldquo;2026-10 · hardware 1.20&amp;rdquo;&lt;/td>
 &lt;td>&amp;ldquo;26.7&amp;rdquo;&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Weight&lt;/strong>&lt;/td>
 &lt;td>The first revision is &lt;code>1000&lt;/code>, and each new one is one lower, so the newest sorts first&lt;/td>
 &lt;td>the same&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Index&lt;/strong>&lt;/td>
 &lt;td>In service: already listed on 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/hardware/">Hardware&lt;/a>; update its Evaluation section. A candidate: add it to 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/evaluations/">Evaluations&lt;/a>&lt;/td>
 &lt;td>Add the item to its layer page, and to 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/evaluations/">Evaluations&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>Add &lt;code>bookCollapseSection: true&lt;/code> to every item page, so its revisions stay folded in the sidebar.&lt;/p></description></item></channel></rss>