# Hotfixes and stability vs cutting-edge functionality
**URL:** https://discourse.cataclysmdda.org/t/hotfixes-and-stability-vs-cutting-edge-functionality/23662
**Category:** The Drawing Board
**Created:** [May 15, 2020, 8:56am UTC](https://discourse.cataclysmdda.org/t/hotfixes-and-stability-vs-cutting-edge-functionality/23662 "2020-05-15T08:56:10Z")
**Posts on this page:** 2
**Page:** 2
### Author:  [@Zhilkin](https://discourse.cataclysmdda.org/u/Zhilkin)
#### Post date: [May 16, 2020, 8:55am UTC](https://discourse.cataclysmdda.org/t/hotfixes-and-stability-vs-cutting-edge-functionality/23662/21 "2020-05-16T08:55:26Z")
> [@Firestorm\_01](#):
>
> Real thing that worrying me is actually that I actually saw the case then player tried to report something to stable, but his issue was closed exactly because it is for stable.
Issues which are non-reproducible on latest master are closed because they are fixed and we do not backport bugfixes. Issues that were confirmed as not fixed on current master are not closed. What’s your concern?
---
### Author:  [@Firestorm\_01](https://discourse.cataclysmdda.org/u/Firestorm_01)
#### Post date: [May 16, 2020, 9:00am UTC](https://discourse.cataclysmdda.org/t/hotfixes-and-stability-vs-cutting-edge-functionality/23662/22 "2020-05-16T09:00:02Z")
> [@Zhilkin](#):
>
> Issues which are non-reproducible on latest master are closed because they are fixed and we do not backport bugfixes. Issues that were confirmed as not fixed on current master are not closed. What’s your concern?
Yes it is correct. No problems there.
But I’ve seen case that it was just closed becasue there is no backporting long time ago (between 0.D and 0.E).
Probably by mistake. Or simply message way too short to explain everything. But it is grabbed my attention.
But frankly it was just one case that I’ve seen. So it is does not really matter now for that case.
If you are closing issues for stable that are fixed or not reproducable- then it is correct.
[Previous page](https://discourse.cataclysmdda.org/t/hotfixes-and-stability-vs-cutting-edge-functionality/23662.md?page=1)