| 2007-02-06 20:19:09 |
Celso Providelo |
bug |
|
|
added bug |
| 2007-02-06 20:19:26 |
Celso Providelo |
soyuz: status |
Unconfirmed |
In Progress |
|
| 2007-02-06 20:19:26 |
Celso Providelo |
soyuz: importance |
Undecided |
Medium |
|
| 2007-02-06 20:19:26 |
Celso Providelo |
soyuz: statusexplanation |
|
|
|
| 2007-02-06 20:19:26 |
Celso Providelo |
soyuz: assignee |
|
cprov |
|
| 2007-02-06 20:24:37 |
Celso Providelo |
bug |
|
|
added subscriber Matthias Klose |
| 2007-03-01 18:00:48 |
Celso Providelo |
soyuz: importance |
Medium |
Low |
|
| 2007-03-01 18:00:48 |
Celso Providelo |
soyuz: assignee |
cprov |
|
|
| 2007-03-01 18:00:48 |
Celso Providelo |
soyuz: statusexplanation |
|
For this time I've queried the database manually for Matthias.
The queries were way more complicated than simply adding IBuild.datebuild, they required join over SSPPH and grouping by SPR.
Maybe querying through Binaries (the opposite end) could simplify them a bit.
Everything suggests it's more like an 'Advanced Source/Binary search' than an "Advanced Build Search" itself. |
|
| 2007-04-23 20:34:58 |
Celso Providelo |
soyuz: status |
In Progress |
Confirmed |
|
| 2007-04-23 20:34:58 |
Celso Providelo |
soyuz: statusexplanation |
For this time I've queried the database manually for Matthias.
The queries were way more complicated than simply adding IBuild.datebuild, they required join over SSPPH and grouping by SPR.
Maybe querying through Binaries (the opposite end) could simplify them a bit.
Everything suggests it's more like an 'Advanced Source/Binary search' than an "Advanced Build Search" itself. |
|
|
| 2007-04-26 12:55:48 |
Celso Providelo |
description |
This feature will allow developers to perform time-aware analysis and build results in the provided contexts (distribution, distrorelease & distroarchrelease)
The main idea is to allow users to restrict build results from time A to time B in addition to the STATE and SOURCENAME.
The timestamp in question will the IBuild.datebuilt for all stable states, unfortunately the provided timestamps won't affect unstable builds (PENDING & BUILDING). |
This feature will allow developers to perform time-aware analysis and build results in the provided contexts (distribution, distrorelease & distroarchrelease)
The main idea is to allow users to restrict build results from time A to time B in addition to the STATE and SOURCENAME.
The timestamp in question will the IBuild.datebuilt for all stable states, unfortunately the provided timestamps won't affect unstable builds (PENDING & BUILDING).
We should also allow the user to type a PACKAGENAME (binary) string which could match resulted binary packages and/or build build dependencies, maybe adding SOURCEVERSION and PACKAGEVERSION to the equation as well.
|
|
| 2007-04-26 12:55:48 |
Celso Providelo |
title |
IHasBuildRecords should support browsing by time |
IHasBuildRecords should support advanced browsing |
|
| 2008-07-04 10:17:08 |
Julian Edwards |
description |
This feature will allow developers to perform time-aware analysis and build results in the provided contexts (distribution, distrorelease & distroarchrelease)
The main idea is to allow users to restrict build results from time A to time B in addition to the STATE and SOURCENAME.
The timestamp in question will the IBuild.datebuilt for all stable states, unfortunately the provided timestamps won't affect unstable builds (PENDING & BUILDING).
We should also allow the user to type a PACKAGENAME (binary) string which could match resulted binary packages and/or build build dependencies, maybe adding SOURCEVERSION and PACKAGEVERSION to the equation as well.
|
This feature will allow developers to perform time-aware analysis and build results in the provided contexts (distribution, distrorelease & distroarchrelease)
The main idea is to allow users to restrict build results from time A to time B in addition to the STATE and SOURCENAME.
The timestamp in question will the IBuild.datebuilt for all stable states, unfortunately the provided timestamps won't affect unstable builds (PENDING & BUILDING).
We should also allow the user to type a PACKAGENAME (binary) string which could match resulted binary packages and/or build build dependencies, maybe adding SOURCEVERSION and PACKAGEVERSION to the equation as well.
Finally - the search for source packages should not match substrings, but complete package names only.
|
|
| 2009-05-09 00:24:49 |
Celso Providelo |
marked as duplicate |
|
231862 |
|
