| 1 |
On Mon, 15 Aug 2016 21:30:04 +0200 |
| 2 |
"Andreas K. Hüttel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> 2) *If* we introduce a "Fixed-in" and maybe an "Introduced-in" field in |
| 5 |
> Bugzilla, which gives a precise $CATEGORY/$PVR where a problem is resolved or |
| 6 |
> introduced, the extraction of fixed or non-fixed bugs might even be |
| 7 |
> automatized. |
| 8 |
|
| 9 |
+1 , this would be useful, but would need some instruction on use |
| 10 |
to ensure people don't just fill it with $LATEST all the time. |
| 11 |
|
| 12 |
The downsides I see from looking at other things that do similar is "broken in" |
| 13 |
is confusing, because 2 or more versions can be broken by given bug, and it can |
| 14 |
become fixed in a subsequent version,....and then broken again. |
| 15 |
|
| 16 |
Leading to the instinct to write: |
| 17 |
|
| 18 |
Broken In: |
| 19 |
1.2 |
| 20 |
1.3 |
| 21 |
1.6 |
| 22 |
|
| 23 |
Fixed In: |
| 24 |
1.4 |
| 25 |
1.5 |
| 26 |
1.7 |
| 27 |
|
| 28 |
Implying "Ranges" instead of specific versions makes their utility weaker as |
| 29 |
far as "bug search" is concerned when one is trying to find "bugs that pertain |
| 30 |
to the thing I'm stabilizing" |
Archives