> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/learn/roadmap/plan-for-2025-2026.md).

# Plan for 2025-2026

Sunbird roadmap planned for 2025-2026

The following is the Roadmap plan for Sunbird over the next one year.

There will be three releases, one new Version, as well as hotfixes/ patches as necessary.

The Sunbird community is encouraged to contribute views and suggestions in the finalization of this roadmap, so that all necessary inputs can be considered before the plan is frozen. 

Please send in your comments regarding the Sunbird 2025-2026 roadmap via the [Discussion Forum thread.  ](https://github.com/orgs/Sunbird-Ed/discussions/760)

**JAN 2025 :** SB Release 7.5

Highlights: Sunbird ED with Easy Installer  (single click install)

**APRIL 2025 :** SB Release 7.6

Highlights: Reference mobile app - android version upgrade, KeyCloak upgrade to ver 21, Security fixes to address critical vulnerabilities

<mark style="color:blue;">**SEPT 2025 : SB Version 8.0**</mark>&#x20;

Highlights :  Improve configurability, Reduce SI customization effort required, Support for new Assessment types, Cross-BB compatibility (Sunbird stack to work with Obsrv 2.0 and RC 2.0)

**DEC 2025 :** SB Release 8.1

Highlights : Incorporate new tech such as AI capabilities into Sunbird for features such as content discovery and recommendations, chat bot functionalities etc.

&#x20;

\ <br>

\ <br>

\
\
\ <br>


---

# 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://ed.sunbird.org/learn/roadmap/plan-for-2025-2026.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.