Difference between revisions of "Feature preview versions"

From Wiki Knowledge Base | Teltonika GPS
(Created page with "= Feature preview versions = Evaluation firmware refers to specialized versions of firmware developed in separate branches during the product development lifecycle. These ve...")
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
__TOC__
+
= Feature preview versions =
   
+
 
== Introduction ==
 
 
Evaluation firmware refers to specialized versions of firmware developed in separate branches during the product development lifecycle. These versions serve as intermediate testing stages before merging new features into the base firmware branch. This approach minimizes the risk of introducing issues into the main firmware and ensures that new features are thoroughly tested by QA teams and delivered faster for clients.
 
Evaluation firmware refers to specialized versions of firmware developed in separate branches during the product development lifecycle. These versions serve as intermediate testing stages before merging new features into the base firmware branch. This approach minimizes the risk of introducing issues into the main firmware and ensures that new features are thoroughly tested by QA teams and delivered faster for clients.
  
Evaluation firmware is released for testing and validation purposes. Once confirmed by QA as stable and functioning correctly, these features are then can planned for future integration into the base firmware.
+
Evaluation firmware is released for testing and validation purposes. Once confirmed by QA as stable and functioning correctly, these features are integrated into the base firmware.
  
== Purpose of evaluation firmware ==
+
== Purpose of Evaluation Firmware ==
 
* '''Isolate new features:''' Ensures the stability of the base firmware by isolating development in separate branches.
 
* '''Isolate new features:''' Ensures the stability of the base firmware by isolating development in separate branches.
 
* '''Thorough testing:''' Allows QA teams to assess new functionality without risking existing features.
 
* '''Thorough testing:''' Allows QA teams to assess new functionality without risking existing features.
 
* '''Early feedback:''' Provides opportunities to identify and resolve issues early in the development process.
 
* '''Early feedback:''' Provides opportunities to identify and resolve issues early in the development process.
  
== List of evaluation firmwares ==
+
== Examples of Evaluation Firmware ==
 
Below are examples of evaluation firmware developed for specific features:
 
Below are examples of evaluation firmware developed for specific features:
  
* '''[https://wiki.teltonika-gps.com/view/Smart_ignition Smart Ignition]'''
+
* [https://wiki.teltonika-gps.com/view/Smart_ignition Smart Ignition] - A specialized firmware to manage ignition control based on external conditions.
* '''[https://wiki.teltonika-gps.com/view/Custom_Scenarios Custom Scenarios]'''
+
* [https://wiki.teltonika-gps.com/view/Custom_Scenarios Custom Scenarios] - Firmware designed to enable user-defined scenarios for flexible device behavior.
  
[[Category:General Information]]
+
== Future Developments ==
 +
This page will be updated with additional evaluation firmware versions as they are developed and tested.

Revision as of 12:21, 29 November 2024

Main Page > General Information > Feature preview versions

Feature preview versions

Evaluation firmware refers to specialized versions of firmware developed in separate branches during the product development lifecycle. These versions serve as intermediate testing stages before merging new features into the base firmware branch. This approach minimizes the risk of introducing issues into the main firmware and ensures that new features are thoroughly tested by QA teams and delivered faster for clients.

Evaluation firmware is released for testing and validation purposes. Once confirmed by QA as stable and functioning correctly, these features are integrated into the base firmware.

Purpose of Evaluation Firmware

  • Isolate new features: Ensures the stability of the base firmware by isolating development in separate branches.
  • Thorough testing: Allows QA teams to assess new functionality without risking existing features.
  • Early feedback: Provides opportunities to identify and resolve issues early in the development process.

Examples of Evaluation Firmware

Below are examples of evaluation firmware developed for specific features:

  • Smart Ignition - A specialized firmware to manage ignition control based on external conditions.
  • Custom Scenarios - Firmware designed to enable user-defined scenarios for flexible device behavior.

Future Developments

This page will be updated with additional evaluation firmware versions as they are developed and tested.