Resolved: This bug has been postponed to future release of PowerShell.

Qustions. Always questions.

How is this resolution? How can we, the reporters, track that it is fixed in
a future version? Must we build our own tracking system for those bugs we
care about? Does anyone else think 'Resolved' is not the correct outcome?

On Thu, 9 Nov 2006 09:55:40 -0800, "public news groups" <null@nil.no>
wrote:

>Qustions. Always questions.
>
>How is this resolution? How can we, the reporters, track that it is fixed in
>a future version? Must we build our own tracking system for those bugs we
>care about? Does anyone else think 'Resolved' is not the correct outcome?

Hi,

As best I understand the process MS have formally to "resolve" every
issue before product release.

One part of that is to decide what's possible to fix / implement in a
particular version of the product. If they decide they can't / won't
implement / fix something then it is "resolved". It's not fixed but at
least it's a conscious (and presumably reasoned) decision not to
prioritise it against other issues that are seen as more important.

As users, we don't always agree with their decisions and when
"resolved" is actually "postponed" it can cause dissatisfaction. But
it's unavoidable at times. If they want to ship by a particular date
they have to make pragmatic decisions.

If you are concerned about a particular issue it might be best to
raise it in a thread which relates only to that issue.

Andrew Watt MVP