# How to properly indicate that a newly documented feature is to be release in the next patch

**URL:** https://discuss.python.org/t/how-to-properly-indicate-that-a-newly-documented-feature-is-to-be-release-in-the-next-patch/57170
**Category:** Documentation
**Tags:** release
**Created:** [July 2, 2024, 11:38am UTC](https://discuss.python.org/t/how-to-properly-indicate-that-a-newly-documented-feature-is-to-be-release-in-the-next-patch/57170 "2024-07-02T11:38:51Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)
#### Post date: [July 2, 2024, 11:56am UTC](https://discuss.python.org/t/how-to-properly-indicate-that-a-newly-documented-feature-is-to-be-release-in-the-next-patch/57170/2 "2024-07-02T11:56:26Z")

</div>

See [Automating versionadded & changed markers in Docs to expedite PRs](https://discuss.python.org/t/38423) 🙂

I asked Hugo (the 3.14 release manager) and he was in favor, provided someone writes the tooling; writing it is on my TODO list.

---

_[View the full topic](https://discuss.python.org/t/how-to-properly-indicate-that-a-newly-documented-feature-is-to-be-release-in-the-next-patch/57170)._