Community
Participate
Working Groups
Addition/changes of timestamp field in bugzilla causes bugs to report false incoming. We should always strip the timezone and if old timestamp as timezone ignore it.
How about correctly convert timezone instead? You can check if local data don't have timezone and only then ignore timezone in the remote changes.
*** Bug 198507 has been marked as a duplicate of this bug. ***
Concerns: * Every install out there that has added a time zone field will have false incoming if we now start dropping the time zone from the timestamp * I'm seeing an offset of -0400 on bugs.eclipse.org/bugs which appears to be the daylight saving offset so if this is changed when no longer daylight savings this will cause false incoming again since the offset is just tacked onto whatever time is returned from the database * I don't see any benefit to doing time zone conversion here and want to avoid any special cases (timezone there / not there) that could complicate code that has taken a while to simplify The ideal solution at this point seems to be to drop the timezone and deal with any potential consequences from installs with time zones. Thoughts?
Marking wontfix. Created bug#202506 to investigate options for forcing connectors to return a standardized format or passing determination of incoming status along to connectors.
*** Bug 193575 has been marked as a duplicate of this bug. ***
