| 1 |
On Sat, 30 Apr 2016 23:16:42 +0200 |
| 2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> just as a small reminder, to ease the load on all arch teams: |
| 5 |
> |
| 6 |
> If a stablerequest has the keyword ALLARCHES set, then |
| 7 |
> * the first arch that tests successfully and stabilizes |
| 8 |
> * can and *should* immediately stabilize for all requested arches! |
| 9 |
|
| 10 |
can => is allowed |
| 11 |
should => may |
| 12 |
|
| 13 |
> Whether this keyword is set on a bug is decision of the package |
| 14 |
> maintainer. |
| 15 |
> |
| 16 |
> For example, Perl team sets ALLARCHES normall for all pure-perl |
| 17 |
> packages (i.e., no compilation / gcc involved). |
| 18 |
|
| 19 |
And it means we're missing opportunities where "pure" interpreted |
| 20 |
packages may test corner cases of the language implementation and find |
| 21 |
bugs in (JIT or previously) "compiled" code. And that means we're |
| 22 |
calling things "stable" that may expose such bugs that turn out not to |
| 23 |
be corner cases at all and affect running systems in unpleasant ways. |
| 24 |
|
| 25 |
|
| 26 |
|
| 27 |
jer |
Archives