> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-7.2.3/pre-release.md). # Pre-Release Before an update is fully released and made available to all the Maitre’D reseller community, it is first released to select few resellers who reported specific issues that are corrected by the new update. The same principle applies to new features. Resellers who originally requested the new feature will be given the chance to “beta-test” new features before they are actually released. Normally, the pre-release period will vary from one week to several weeks, depending on the number of bug fixes or the complexity of the new features to be released. If an issue is discovered during the pre-release phase, corrections will be made and the pre-release period will be extended as necessary. --- # 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://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-pa-dss-implementation-guide/pa-dss-requirement-7.2.3/pre-release.md?ask=&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.