: Re: Should the documentation of a known issue change dependent on the stability of a product release? I am writing the release documentation for a software product and a design flaw has been discovered
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.
More posts by @Mendez196
: Have there been any studies indicating which software documentation practices save the most time during onboarding? It's generally conceded that at least some documentation saves people time when
: How can a "rip-off" still be good? This time, I'm not really talking about the legal side (that has already been covered a few times here), but more about what the readers and the critics
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.