> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/getting-started/general-information/logicnets-version-numbering-release-and-maintenance-policy.md).

# LogicNets' Version Numbering, Release, and Maintenance Policy

## Version Numbering

The version notation for LogicNets’ platform software consists of three numbers in the order X.Y.Z.

* X stands for the major version. It designates a significant change in the LogicNets platform (e.g. like a step from Windows 7 to Window 10).
* Y stands for the minor version. It designates new features added to the LogicNets platform that are of moderate nature.
* Z stands for a sub (intermediate)-version and is closely tied our release strategy.

Additionally, there is a revision number next to the X.Y.Z number. The revision number is tied to our code archive and serves as a link between a software release and the code in the archive.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-d21a7893fda095c0addb5f6426a3a307a3676078%2F05054143-8f73-4f6f-ae6d-4f90cf122d99.png?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-cd6b0313c68c6625be2d80408483d0729f2c1c3f%2Fdc9993ca-c7b4-45d3-a807-639a81c66a6c.png?alt=media)

## Release Strategy

The scope of each X.Y release is derived from the LogicNets product roadmap. An X.Y release is released in a staged approach:

* The first version(s) is shared with a small group of customers (Limited Release). These customers are either early adopters participating in a beta program or customers who are actively involved in trying out the new platform features.
  * In some cases, these first versions may contain only a subset of the planned features of the release.
  * Development continues after Limited Release until all scoped features are finalized.
* Once all scoped features are finalized, LogicNets creates a Generally Available version of the release, which becomes the active platform release. By its definition, this release is generally available for the LogicNets' customer base.
  * Official release notes are distributed for this version.
  * Customers who received earlier sub (intermediate)-versions of the X.Y release are actively rolled up to the GA release.

## Maintenance Strategy

* LogicNets performs active support and maintenance on all Generally Available versions made available within the past two years. In addition, LogicNets retires Generally Available versions after a period of two years.
  * LogicNets advises customers to regularly upgrade to the latest release, as each release includes many useful improvements.
* LogicNets resolves Critical and Major bugs on all active releases. Minor and moderate issues are resolved only on the currently active release.
* Minor, moderate, major, and critical issues will be resolved in releases depending on the phase of the release and how it applies to our contractual SLAs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/getting-started/general-information/logicnets-version-numbering-release-and-maintenance-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.