Forum Suggestion - Known Bugs and expected build - sticky
How about a sticky being put in here to cover the known bugs in the product and the expected release build that should address them.
The reason I suggest this is that in a number of cases issues are identified and the support comment is a positive that it is now known and will be fixed either in the next hotfix, next update, minor upgrade etc. However to end users we have no idea if that means next week, next month or next year.
That can then mean with each update the issue is re-reported and/or tested and found not to be in that update.
As each item is reported and acknowledged the sticky would get updated with the new issue. As the issue passes through development and QA the build it is fixed or expected to be fixed in could be updated.
Additionally we can use it as a check before reporting an issue, so you don't get multiple reports of the AD issue in build 7004 for instance.
Also the support team may be aware of issues that come in through the support desk rather than these forums and this could be a conduit for making those issues public if needs be.
Maybe it is all too cumbersome an idea, and something better can be suggested.
Is it feasible without tying up resources that would be better deployed actually working on the product for the good of us all?
Should there be versions per Major product line, V5, 6 7 etc?
Regards,
Andy
The reason I suggest this is that in a number of cases issues are identified and the support comment is a positive that it is now known and will be fixed either in the next hotfix, next update, minor upgrade etc. However to end users we have no idea if that means next week, next month or next year.
That can then mean with each update the issue is re-reported and/or tested and found not to be in that update.
As each item is reported and acknowledged the sticky would get updated with the new issue. As the issue passes through development and QA the build it is fixed or expected to be fixed in could be updated.
Additionally we can use it as a check before reporting an issue, so you don't get multiple reports of the AD issue in build 7004 for instance.
Also the support team may be aware of issues that come in through the support desk rather than these forums and this could be a conduit for making those issues public if needs be.
Maybe it is all too cumbersome an idea, and something better can be suggested.
Is it feasible without tying up resources that would be better deployed actually working on the product for the good of us all?
Should there be versions per Major product line, V5, 6 7 etc?
Regards,
Andy