# Versioning Best Practices

​Effective management of knowledge base (KB) versions is essential to ensure the accuracy and reliability of knowledge bases. The following guidelines provide best practices for implementing version control strategies.

## **Versioning Best Practices**

Consider the following strategies to maintain and implement robust version control:

* **Single Editor Policy**: Allow only one individual to edit a KB at any given time to prevent saving conflicts and lost progress.​
* **Incremental Changes**: Make small, manageable updates to facilitate easier tracking and reduce the risk of errors.​ Implement change-check-test, development process. See [configuration tips](/setting-up/configure-knowledge-base/configuration-tips.md) for more information.
* **Frequent Saves**: Regularly save changes to minimize data loss and maintain an up-to-date record of modifications.​
* **Regular Testing**: Consistently test the KB after updates to verify functionality and accuracy.​
* **A/B Testing**: Implement A/B testing methodologies to evaluate the effectiveness of different KB versions and identify the most user-friendly formats.
* **Consistent Naming Conventions**: Adopt a standardized naming system for KB versions to streamline organization and retrieval. For example, use the format: `<Knowledge_Base_Name>_<Version_Number>`.​ For example "Demo Procurement KB V2.1"

<figure><img src="/files/bLRGDCeuVbpzLxUim2o4" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lumi-ai.com/using-lumi/best-practices/versioning-best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.