1 |
On Mon, 2006-10-30 at 00:28 -0800, Robin H. Johnson wrote: |
2 |
> On Sun, Oct 29, 2006 at 07:49:22PM -0700, Jason Wever wrote: |
3 |
> > Please triple check what you want to commit and verify that you don't do |
4 |
> > any of the following (which are punishable by death): |
5 |
> > |
6 |
> > 1) remove the last ebuild that is keyworded for a given arch, especially |
7 |
> > when resulting in broken dependencies. |
8 |
> > |
9 |
> > 2) remove the last stable ebuild for an architecture |
10 |
> > |
11 |
> > 3) remove the last testing ebuild for an architecture when there is no |
12 |
> > stable ebuild available after the removal |
13 |
> |
14 |
> To generalize on Francesco's email, how long should developers wait for |
15 |
> minority arches to mark stuff stable, after a security bug, and then a |
16 |
> reminder more than 4 months later? 5 months of no response from the |
17 |
> arches says something is wrong on their side. |
18 |
> |
19 |
I might be mistaken, but I believe sparc responds pretty quickly to |
20 |
security bugs, either by taking the requested action or by explaining |
21 |
why the requested action is impossible (i.e., build problems). |
22 |
|
23 |
> I think that usage statistics might point out that there are nobody even |
24 |
> using these specific ebuilds that are proposed for removal. |
25 |
> |
26 |
|
27 |
Regards, |
28 |
-- |
29 |
Ferris McCormick (P44646, MI) <fmccor@g.o> |
30 |
Developer, Gentoo Linux (Devrel, Sparc) |