| 1 |
> No, not really. Just that I'd expect kinda more proactive approach than |
| 2 |
> the one demonstrated fex. in |
| 3 |
> http://bugs.gentoo.org/show_bug.cgi?id=128588#c29 (and a bit more |
| 4 |
> flexible approach to other alternatives, such as HW/hosting offers we've |
| 5 |
> received before) and that have been declined for various strange reasons. |
| 6 |
|
| 7 |
Linking to a bug where you make crazed comments about how bugs isn't |
| 8 |
fixed!!!!1111oneone and that dammit someone should do something |
| 9 |
now!!!1111 doesn't really help your case. |
| 10 |
|
| 11 |
I bet if I was infra I'd be wondering what my options were since: |
| 12 |
|
| 13 |
bugs is a pretty critical part of developing; AND |
| 14 |
you can't just host it anywhere; AND |
| 15 |
the hardware needed for it to perform is expensive; AND |
| 16 |
they did not know what the problem was at first |
| 17 |
|
| 18 |
As in, you don't just grab the first dual proc system that was offered |
| 19 |
out of some guys basement to host bugs on. You need a dedicated host |
| 20 |
who will stick around and provide good support should something go |
| 21 |
wrong. You need expensive hardware ( I believe we got a blade server |
| 22 |
with 3 blades in it, which is fscking expensive if you haven't priced |
| 23 |
one out before ). So once again, chill out. They are working on it. |
| 24 |
|
| 25 |
And yes bugs is slow and yes it sucks, but bitching about it doesn't |
| 26 |
accomplish anything :x |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives