Whoops - Critical bug found in JIRA 4.4.2
Thursday, 13 October 2011 19:26
We all strive for perfection, but sometimes things slip through the cracks. Unfortunately, today is one of those days.Due to an unexpected bug, we have taken down the JIRA 4.4.2 release. As a result, GreenHopper 5.8 is also on hold because it is dependent on JIRA 4.4.2. Other versions of JIRA are not affected by this issue.
What is the problem?
This bug in JIRA 4.4.2 can cause data corruption on high load servers where lots of new issues are being created simultaneously. Details can be found here: JRA-25914What if I already upgraded to JIRA 4.4.2?
For any JIRA customer who has already upgraded to JIRA 4.4.2, we recommend that you roll back to your previous version as soon as possible. If you are not able to roll back, please contact Atlassian Support for further instructions.
Please stay tuned
Please watch this blog as we will be updating it to provide more information as it becomes available.
Read more http://feedproxy.google.com/~r/JIRABlog/~3/AgtI1dARZBk/whoops---critical-bug-found-in-jira-442.html
