| 1 |
On Saturday, August 06, 2011 07:49:21 Fabian Groffen wrote: |
| 2 |
> On 06-08-2011 11:00:16 +0100, Markos Chandras wrote: |
| 3 |
> > Oh come on Jorge. You know what I mean by slacking arches. I am not |
| 4 |
> > talking about punishing them. Maybe drop stable keywords or drop keyword |
| 5 |
> > from X package and shrink their tree so they can keep up with the load. |
| 6 |
> > |
| 7 |
> > > This should be the arch more developers use daily and is likely the |
| 8 |
> > > one with more members (herd count). Also, one should remember the |
| 9 |
> > > time it takes to compile, test or debug an issue in a recent amd64 |
| 10 |
> > > system or an old / slow box with an "exotic arch" varies |
| 11 |
> > > substantially. Not to mention that the amount of testing done on |
| 12 |
> > > "exotic arches" varies substantially between projects. |
| 13 |
> > |
| 14 |
> > I am aware of the problems and this is way I want a solution. |
| 15 |
> |
| 16 |
> And what solution do you have in mind (in your Council role)? |
| 17 |
|
| 18 |
automated build boxes + better tools for marking packages stable. a command |
| 19 |
line interface that let's you view pending stable requests in a condensed |
| 20 |
format and quickly approve from right there (which would post a comment and |
| 21 |
mark the respective ebuild stable for you). |
| 22 |
|
| 23 |
a significant chunk of time wasted on keeping packages keyworded stable is the |
| 24 |
bugzilla interface and actually going into the cvs tree to make the stable |
| 25 |
change and commit it. |
| 26 |
-mike |
Archives