Update webpage "About" from version "8.1.0" to "8.2.0"
This commit is contained in:
parent
44ba9a7611
commit
910e2686ae
SSH Key Fingerprint:
SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
150
about.xhtml
150
about.xhtml
@ -1,7 +1,7 @@
|
||||
<!DOCTYPE html>
|
||||
|
||||
<!-- Inferencium - Website - About -->
|
||||
<!-- Version: 8.1.0 -->
|
||||
<!-- Version: 8.2.0 -->
|
||||
|
||||
<!-- Copyright 2022 Jake Winters -->
|
||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||
@ -350,54 +350,46 @@
|
||||
<h3><a href="#versioning-phases">What Are the Phases?</a></h3>
|
||||
<p>There are 4 phases of development. Each phase typically has
|
||||
its own branch in each source code repository. The phases are as
|
||||
follows:
|
||||
<ol>
|
||||
<li>Alpha: Pre-alpha development and alpha
|
||||
testing occurs in this phase. Features are
|
||||
added, modified, and/or removed. Fixes and
|
||||
optimisations may also occur if they are caught
|
||||
during this phase. This is where the majority of
|
||||
changes occur and where the fine-grained commits
|
||||
can be found. Breakage is highly likely within
|
||||
this phase as it makes no attempt to be stable
|
||||
or usable due to being where the most rapid
|
||||
development occurs. Code is tested internally in
|
||||
a fine-grained manner and is moved to the next
|
||||
phase only when it is deemed feature-complete
|
||||
and reasonably stable for broader public
|
||||
testing. If you would like to assist in testing
|
||||
code in this phase, you must use the code and/or
|
||||
tags from the source code repositories due to it
|
||||
not being available publicly outside of
|
||||
them.</li>
|
||||
<li>Beta: Feature-complete testing occurs in
|
||||
this phase. Only bug fixes and optimisations
|
||||
occur in this phase, such as stability and
|
||||
security fixes. This phase is classified as
|
||||
stable enough for broad public testing and is
|
||||
made available publicly in many cases without
|
||||
having to use the source code repositories.
|
||||
Since this phase contains only feature-complete
|
||||
code, no features will be added, modified, or
|
||||
removed in this phase.</li>
|
||||
<li>Release candidate (RC): Feature-complete
|
||||
testing occurs in this phase. Code in the RC
|
||||
phase is often stable enough for production
|
||||
usage, but is not yet completely acceptable to
|
||||
be classified as stable by my standards. This
|
||||
phase is often skipped due to most bugs being
|
||||
caught in the beta phase, but will be used
|
||||
should the need arise for finer-grained testing
|
||||
beyond what the beta phase can provide. Like the
|
||||
beta phase, code in this phase is available
|
||||
publicly without requiring usage of the source
|
||||
code repositories.</li>
|
||||
<li>Stable: Feature-complete and well-tested
|
||||
code is moved to this phase. Code in this phase
|
||||
is deemed to be stable enough for production
|
||||
usage and full support is provided.</li>
|
||||
</ol>
|
||||
</p>
|
||||
follows:</p>
|
||||
<ol>
|
||||
<li>Alpha: Pre-alpha development and alpha testing
|
||||
occurs in this phase. Features are added, modified,
|
||||
and/or removed. Fixes and optimisations may also occur
|
||||
if they are caught during this phase. This is where the
|
||||
majority of changes occur and where the fine-grained
|
||||
commits can be found. Breakage is highly likely within
|
||||
this phase as it makes no attempt to be stable or usable
|
||||
due to being where the most rapid development occurs.
|
||||
Code is tested internally in a fine-grained manner and
|
||||
is moved to the next phase only when it is deemed
|
||||
feature-complete and reasonably stable for broader
|
||||
public testing. If you would like to assist in testing
|
||||
code in this phase, you must use the code and/or tags
|
||||
from the source code repositories due to it not being
|
||||
available publicly outside of them.</li>
|
||||
<li>Beta: Feature-complete testing occurs in this phase.
|
||||
Only bug fixes and optimisations occur in this phase,
|
||||
such as stability and security fixes. This phase is
|
||||
classified as stable enough for broad public testing and
|
||||
is made available publicly in many cases without having
|
||||
to use the source code repositories. Since this phase
|
||||
contains only feature-complete code, no features will be
|
||||
added, modified, or removed in this phase.</li>
|
||||
<li>Release candidate (RC): Feature-complete testing
|
||||
occurs in this phase. Code in the RC phase is often
|
||||
stable enough for production usage, but is not yet
|
||||
completely acceptable to be classified as stable by my
|
||||
standards. This phase is often skipped due to most bugs
|
||||
being caught in the beta phase, but will be used should
|
||||
the need arise for finer-grained testing beyond what the
|
||||
beta phase can provide. Like the beta phase, code in
|
||||
this phase is available publicly without requiring usage
|
||||
of the source code repositories.</li>
|
||||
<li>Stable: Feature-complete and well-tested code is
|
||||
moved to this phase. Code in this phase is deemed to be
|
||||
stable enough for production usage and full support is
|
||||
provided.</li>
|
||||
</ol>
|
||||
<p>When development of a new version has begun, the code within
|
||||
the alpha phase is rebased onto the most recent code from the
|
||||
stable phase before work commences. This cycle continues for the
|
||||
@ -687,9 +679,10 @@
|
||||
secure-by-default, Android-based operating
|
||||
system which implements extensive, systemic
|
||||
security and privacy hardening to the Android
|
||||
Open Source Project used as its base codebase.
|
||||
Its hardening includes closing gaps for apps to
|
||||
access sensitive system information, a secure
|
||||
Open Source Project used as its base
|
||||
codebase.</p>
|
||||
<p>Its hardening includes closing gaps for apps
|
||||
to access sensitive system information, a secure
|
||||
app spawning feature which avoids sharing
|
||||
address space layout and other secrets AOSP's
|
||||
default Zygote app spawning model would share,
|
||||
@ -705,11 +698,11 @@
|
||||
to ensure the OS has not been corrupted or
|
||||
tampered with.</p>
|
||||
<p>GrapheneOS only supports
|
||||
<a href="https://grapheneos.org/faq#device-support">high security and well-supported devices</a>
|
||||
<a href="https://grapheneos.org/faq#device-support">high-security and well-supported devices</a>
|
||||
which receive full support from their
|
||||
manufacturers, including firmware updates, long
|
||||
support lifecycles, secure hardware, and overall
|
||||
high security practices.</p>
|
||||
high-security practices.</p>
|
||||
<p>For an extensive list of features GrapheneOS
|
||||
provides, visit its
|
||||
<a href="https://grapheneos.org/features/">official features list</a>
|
||||
@ -728,12 +721,12 @@
|
||||
</th>
|
||||
<td class="desc" headers="software-smartphone-description vanadium">
|
||||
<p>Vanadium is a security-hardened,
|
||||
privacy-hardened Chromium-based web browser
|
||||
privacy-hardened, Chromium-based web browser
|
||||
which utilises GrapheneOS' operating system
|
||||
hardening to implement stronger defenses to the
|
||||
already very secure Chromium web browser. Its
|
||||
hardening alongside Chromium's base security
|
||||
features includes
|
||||
already very secure Chromium web browser.</p>
|
||||
<p>Its hardening alongside Chromium's base
|
||||
security features includes
|
||||
<a href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/0081-Implement-UI-for-JIT-site-settings.patch">disabling JavaScript just-in-time (JIT) compilation by default</a>,
|
||||
<a href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/0051-stub-out-the-battery-status-API.patch">stubbing out the battery status API to prevent abuse of it</a>,
|
||||
and
|
||||
@ -767,18 +760,15 @@
|
||||
to protect user keys using the device's hardware
|
||||
security module.</p>
|
||||
<p>Molly is available in
|
||||
<a href="https://github.com/mollyim/mollyim-android#free-and-open-source">2 flavours</a>:
|
||||
<ul>
|
||||
<li>Molly, which includes the
|
||||
same proprietary Google code as
|
||||
Signal to support more
|
||||
features.</li>
|
||||
<li>Molly-FOSS, which removes
|
||||
the proprietary Google code to
|
||||
provide an entirely open-source
|
||||
client.</li>
|
||||
</ul>
|
||||
</p>
|
||||
<a href="https://github.com/mollyim/mollyim-android#free-and-open-source">2 flavours</a>:</p>
|
||||
<ul>
|
||||
<li>Molly, which includes the same
|
||||
proprietary Google code as Signal to
|
||||
support more features</li>
|
||||
<li>Molly-FOSS, which removes the
|
||||
proprietary Google code to provide an
|
||||
entirely open-source client</li>
|
||||
</ul>
|
||||
</td>
|
||||
<td headers="software-smartphone-source_model molly">
|
||||
Open-source<br/>
|
||||
@ -802,6 +792,26 @@
|
||||
(GPL-3.0-only)
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<th id="software-smartphone-viewer">Viewer</th>
|
||||
<th id="gallery" headers="software-smartphone software-smartphone-viewer">
|
||||
<img src="asset/img/logo-gallery.png" width="100" height="100" alt="Gallery logo"/><br/>
|
||||
Gallery
|
||||
</th>
|
||||
<td class="desc" headers="software-smartphone-description gallery">
|
||||
<p><a href="https://github.com/IacobIonut01/Gallery">Gallery</a>
|
||||
is a lightweight image and video viewer with
|
||||
image editing capabilities.</p>
|
||||
<p>It has a clean and modern design without
|
||||
including unnecessary features, and runs
|
||||
smoothly. It provides both individual image and
|
||||
video file view, and folder view.</p>
|
||||
</td>
|
||||
<td headers="software-smartphone-source_model gallery">
|
||||
Open-source<br/>
|
||||
(Apache-2.0)
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
BIN
asset/img/logo-gallery.png
Normal file
BIN
asset/img/logo-gallery.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 13 KiB |
Loading…
x
Reference in New Issue
Block a user