AnsweredAssumed Answered

Community Edition bugs need validation on 4.2.c

Question asked by jpotts Moderator on Dec 14, 2012
We have identified a collection of Jira issues that have been reported against Community Edition after 3.1 but before 4.2 that either lack enough information to be recreated or have not been seen by the QA team or any customers using Enterprise Edition.

We want to make sure that valid issues that still exist in 4.2.c Community Edition have a better chance of getting addressed. To do that, we need to reduce the queue of issues that may no longer be valid.

We're going to set the issues to "Need more info" so that the original reporter is notified, but because some are quite old, there is a chance the original reporter has moved on to other things and won't have any interest in providing additional information. I'm hoping maybe some people in the community will be interested in helping us validate some of these issues.

If you want to help, you can take a look at the list and then comment on the issue with your testing results. It might be something like, "Yes, this is still a bug on 4.2.c and here are the steps to reproduce it" or it might be "Unable to reproduce on 4.2.c" or "Needs more information" etc.

If possible, we'd like this to happen by 12/21. Any issues on this list that can't be re-produced will be closed out on 12/28. They can always be re-opened if they crop up again.

Thanks for any help you can provide,