| 2012-03-19 22:24:02 |
Eike |
bug |
|
|
added bug |
| 2012-03-19 22:24:03 |
Eike |
bug-repo-syncer: importance |
Undecided |
Wishlist |
|
| 2012-03-19 22:24:03 |
Eike |
bug-repo-syncer: milestone |
|
0.4.0 |
|
| 2012-03-19 22:24:04 |
Eike |
summary |
dummy |
Represent Bug Status Values as Sets |
|
| 2012-03-19 22:24:04 |
Eike |
description |
dummy |
The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.
Therefore the status values should be represented with a set of possible
values, with a preferred or default value.
Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.
Before uploading the bug, the set is exchanged by its default value.
See:
Bug #303 |
|
| 2012-03-25 22:50:33 |
Eike |
description |
The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.
Therefore the status values should be represented with a set of possible
values, with a preferred or default value.
Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.
Before uploading the bug, the set is exchanged by its default value.
See:
Bug #303 |
The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.
Therefore the status values should be represented with a set of possible
values, with a preferred or default value.
Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.
Before uploading the bug, the set is exchanged by its default value.
See:
[@[@BUGLINK "Bug #303"@lp @]@]
bug #949820 |
|
| 2012-03-29 09:20:54 |
Eike |
description |
The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.
Therefore the status values should be represented with a set of possible
values, with a preferred or default value.
Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.
Before uploading the bug, the set is exchanged by its default value.
See:
[@[@BUGLINK "Bug #303"@lp @]@]
bug #949820 |
The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.
Therefore the status values should be represented with a set of possible
values, with a preferred or default value.
Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.
Before uploading the bug, the set is exchanged by its default value.
See:
bug #949820 |
|
| 2012-04-01 10:44:26 |
Eike |
bug-repo-syncer: milestone |
0.4.0 |
0.5.0 |
|
