| 2012-03-08 10:22:34 |
Eike |
bug |
|
|
added bug |
| 2012-03-08 10:22:42 |
Eike |
bug-repo-syncer: importance |
Undecided |
Low |
|
| 2012-03-08 10:22:48 |
Eike |
bug-repo-syncer: milestone |
|
0.3.0 |
|
| 2012-03-08 11:55:04 |
Eike |
bug-repo-syncer: importance |
Low |
Wishlist |
|
| 2012-03-08 11:55:04 |
Eike |
summary |
Conserve Launchpad's bug status values |
Conserve Launchpad's bug status values |
|
| 2012-03-19 17:41:55 |
Eike |
bug-repo-syncer: status |
New |
Confirmed |
|
| 2012-03-19 22:23:59 |
Eike |
bug-repo-syncer: milestone |
0.3.0 |
0.4.0 |
|
| 2012-03-19 22:23:59 |
Eike |
description |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Incomplete (with response)",
"Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength. |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Incomplete (with response)",
"Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
Bug #311 |
|
| 2012-03-25 22:50:28 |
Eike |
description |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Incomplete (with response)",
"Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
Bug #311 |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Incomplete (with response)",
"Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
|
| 2012-03-29 09:18:31 |
Eike |
description |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released", "Incomplete (with response)",
"Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released",
"Incomplete (with response)", "Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
|
| 2012-03-29 09:19:19 |
Eike |
description |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released",
"Incomplete (with response)", "Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" would get a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released",
"Incomplete (with response)", "Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" gets a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
|
| 2012-03-29 09:21:21 |
Eike |
description |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released",
"Incomplete (with response)", "Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" gets a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
[@[@BUGLINK "Bug #311"@lp @]@]
bug #959770 |
Bug Repo Syncer has internally only 4 status values, while Launchpad has 14
status values. Several of Launchpad's status values are considered equivalent
to one internal status value. For example: "New", "Incomplete" -> "new".
Internal Status Values:
"new", "confirmed", "in_progress", "closed"
Launchpad's Status Values:
"New", "Incomplete", "Opinion", "Invalid", "Won't Fix", "Expired",
"Confirmed", "Triaged", "In Progress", "Fix Committed", "Fix Released",
"Incomplete (with response)", "Incomplete (without response)", "Unknown"
Currently when bugs are updated in Launchpad, the status values are adapted to
the much simpler internal model. A bug with status "Incomplete" gets a new
status of "New". This leads to loss of information on information on Launchpad.
'''Therefore:'''
Don't overwrite bug status values on Launchpad, when they are compatible with
the internal status values.
The architecture of Launchpadlib makes this possible without further slowdown
(I think). Every bug on Launchpad is downloaded anyway before it can be
updated. Therefor the program can look at the bug status before it is changed.
It would turn Launchpadlib's slowness into its strength.
See also:
bug #959770 |
|
| 2012-04-01 10:46:05 |
Eike |
bug-repo-syncer: milestone |
0.4.0 |
0.5.0 |
|
