I think in addition to change log we heed know issues page which would help everyone avoid upgrading to releases with bugs that could be production impacting. and please dont tell me that dev instance is for testing etc. i dont wont to test anything if its already known to be broken.
recent undocumented changes in api json structure or (known to support) broken recurring/schedule downtime feature really cost me time to fix or create workarounds.
Known issues
Re: Known issues
It is never our intent to release a product with "known" issues or any issues for that matter. However, it takes time for our developers to fix the bugs, and for our QA team to test the bug fixes.
If bugs cannot be fixed right away, they are fixed in the next release or a patch/workaround is provided.
If bugs cannot be fixed right away, they are fixed in the next release or a patch/workaround is provided.
This is your choice but I would like to point out that it is ALWAYS a good idea to try a new release in a test environment prior to upgrading a production system.and please dont tell me that dev instance is for testing etc. i dont wont to test anything if its already known to be broken.
Be sure to check out our Knowledgebase for helpful articles and solutions!