Post History
Beta or not does not matter, whether a patch exists does not matter, write it up. Document it. Like your previous question, this is a business matter, not a documentation issue you should decide f...
Answer
#4: Attribution notice removed
by
System
·
2019-12-19T22:13:19Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33263 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T07:57:37Z (almost 5 years ago)
Source: https://writers.stackexchange.com/a/33263 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
## Beta or not does not matter, whether a patch exists does not matter, write it up. Document it. Like your previous question, this is a **business matter,** not a documentation issue you should decide for yourself. You should document it, even if you have just ONE beta tester, whether or not a patch exists, and let your management decide if they are willing to risk any liability or negative publicity that may arise from a **failure** to document the behavior. This should not be **your** decision, it should be the decision of somebody with fiscal responsibility for the fate of your company or employer.
#1: Imported from external source
by
System
·
2018-02-14T14:28:45Z (over 6 years ago)
Original score: 3