CDR Tickets

BZDATETIME::2010-05-24 10:38:11
BZCOMMENTOR::Bob Kline
BZCOMMENT::1

Changed target version (you probably don't want to wait until we port the CDR Server to .NET for this new value to be added).

Volker:

Please remove the 2.0 target. Kim's not the only one to have tripped up on this. We can add it back in when it's clear we'll really build it. Of course, it may not be possible to remove it if there are issues targeted to that release. In that case, you can see if the targets are all bogus. If so, please fix them. If there are issues which are correctly targeted to 2.0, then we'll just have to leave it in place and remind users to be careful when they create new issues.

BZDATETIME::2010-05-24 11:04:31
BZCOMMENTOR::Admin (VEnglisch)
BZCOMMENT::2

(In reply to comment #1)
> Of course, it may not be possible to remove it if there are issues
> targeted to that release.

Correct.
There are 32 issues linked to version 2.0. 28 of those are closed and probably bogus but at least 2 of the remaining open issues are legitimate.
Still, if you think this is serious enough I don't see anything wrong with setting the issues for the .Net port to V1.0 for the time being until we start actively working on those.
Here is the list of issues with Version 2.0
http://verdi.nci.nih.gov/tracker/buglist.cgi?version=2.0&product=CDR

BZDATETIME::2010-05-24 11:18:28
BZCOMMENTOR::Bob Kline
BZCOMMENT::3

I have fixed the bogus targets. Let's leave the target in place (for the benefit of the two legitimate 2.0 issues) and just remind users to be careful about the target assigned to new issues.

BZDATETIME::2010-05-24 11:27:51
BZCOMMENTOR::Volker Englisch
BZCOMMENT::4

I guess we need to notify the users entering a 2.0 version because Bugzilla's rule is: Save the settings from the last submission of a bug.
If you submit a new bug with version 2.0 it will always submit the following bugs with version 2.0 unless it's changed by the person submitting the bug because the parameter settings are stored in the cookies.

BZDATETIME::2010-05-25 09:06:20
BZCOMMENTOR::Kim Eckley
BZCOMMENT::5

(In reply to comment #4)
> I guess we need to notify the users entering a 2.0 version because Bugzilla's
> rule is: Save the settings from the last submission of a bug.
> If you submit a new bug with version 2.0 it will always submit the following
> bugs with version 2.0 unless it's changed by the person submitting the bug
> because the parameter settings are stored in the cookies.

I'll try to remember this with any future issues.

Now, for the value, any issues?

BZDATETIME::2010-05-25 09:32:42
BZCOMMENTOR::Bob Kline
BZCOMMENT::6

Installed on Mahler; ready for user review.

BZDATETIME::2010-05-25 10:07:05
BZCOMMENTOR::Kim Eckley
BZCOMMENT::7

(In reply to comment #6)
> Installed on Mahler; ready for user review.

Verified - promote to BACH

BZDATETIME::2010-05-25 11:54:43
BZCOMMENTOR::Bob Kline
BZCOMMENT::8

Do you really want Microsoft's fancy hyphen in the new value (instead of the plain ASCII version)?

BZDATETIME::2010-05-25 13:10:42
BZCOMMENTOR::Kim Eckley
BZCOMMENT::9

(In reply to comment #8)
> Do you really want Microsoft's fancy hyphen in the new value (instead of the
> plain ASCII version)?

I just typed - didn't realize there was a difference. If ASCII is preferred, it is perfectly fine with me!

BZDATETIME::2010-05-25 14:08:29
BZCOMMENTOR::Bob Kline
BZCOMMENT::10

Fixed on Mahler. Which browser did you use when you typed the value in? I was aware that Microsoft had Word munging what users typed, but I didn't realize they had extended this behavior to Internet Explorer.

BZDATETIME::2010-05-25 14:15:43
BZCOMMENTOR::Kim Eckley
BZCOMMENT::11

(In reply to comment #10)
> Fixed on Mahler. Which browser did you use when you typed the value in? I was
> aware that Microsoft had Word munging what users typed, but I didn't realize
> they had extended this behavior to Internet Explorer.

I am using IE7.

Verified in Mahler.

BZDATETIME::2010-05-26 11:02:02
BZCOMMENTOR::Bob Kline
BZCOMMENT::12

Promoted to Bach; please check (and close if OK).

BZDATETIME::2010-05-26 11:10:39
BZCOMMENTOR::Kim Eckley
BZCOMMENT::13

(In reply to comment #12)
> Promoted to Bach; please check (and close if OK).

Verified, closed.

Thanks!

BZDATETIME::2010-05-27 09:20:15
BZCOMMENTOR::Bob Kline
BZCOMMENT::14

Attempting to reproduce the IE bug Kim ran into (IE replaced the ASCII hyphen she typed into the browser's form window - with the UNICODE [EN DASH] character).

BZDATETIME::2010-05-27 10:31:06
BZCOMMENTOR::Bob Kline
BZCOMMENT::15

(In reply to comment #14)
> Attempting to reproduce the IE bug Kim ran into (IE replaced the ASCII hyphen
> she typed into the browser's form window - with the UNICODE [EN DASH]
> character).

Unable to reproduce that behavior. I suspect that the user pasted clipboard contents generated by another application (as opposed to typing the ASCII hyphen character directly into IE).

BZDATETIME::2010-05-27 10:43:17
BZCOMMENTOR::Kim Eckley
BZCOMMENT::16

(In reply to comment #15)
> (In reply to comment #14)
> > Attempting to reproduce the IE bug Kim ran into (IE replaced the ASCII hyphen
> > she typed into the browser's form window - with the UNICODE [EN DASH]
> > character).
> Unable to reproduce that behavior. I suspect that the user pasted clipboard
> contents generated by another application (as opposed to typing the ASCII
> hyphen character directly into IE).

Quite possible that I copied from an Outlook email.