vmiklos:

I commited a basic set of instructions for it. It may need correcting to get it 
right. I can't test it right now.

bouleetbil:

I feel like I'm being attacked over this whole matter. Yes, it's my fault. But 
I've done everything I could
conceive of to fix the problems I created. Does this count for anything at all? 
My main reluctance with
your absolute solution is that it doesn't make any allowances for minor bumps.

AFAIK, when vmiklos was doing his minor kernel bumps, he never had to make any 
sort of WIP. The ones
I've seen most likely to break shit in base are: glibc, udev, major kernel 
bumps, and systemd. The only thing
I can really agree with is that we need more testing for most changes, but 
generally I think it's overkill to
require many developers to test every single change to base. This adds more 
overhead to getting stuff done.

I remember just trying to get major kernel bumps done. Just doing an email to 
devel about it generally gets
few replies. Generally I might get a maximum of 3 replies within a reasonable 
time frame. The last kernel
bump to 3.1 only got a single one from mcirsta. See here: 
http://frugalware.org/pipermail/frugalware-devel/2011-October/thread.html#11044

So, it boils down to my main resistance which is due to the lack of interest I 
get from other developers. I got
fed up with getting few if any responses to my WIPs, to the point that I only 
wanted to bother with it for very
major kernel rebuilds or similar massive projects. I hate doing it for changes 
I perceive to be relatively minor;
where a simple test as instructed to me by vmiklos would probably suffice.

Your main objection seems to be about the possibility of stealth breakages. I 
know that happened here. I tested
the new udev to the extent that I could, but it still blew up in my face when 
others had issues. The problem was
rooted in the fact that the new udev broke firmware loading for modules. I 
reverted it to the previous working
version as soon as I heard about it. I'm truely sorry, but what else can I do? 
Ultimately, no one can guarantee any
changes they make won't bring it to a screeching halt.

Now that I've had a chance to expression my full feelings and position on this, 
what can we do to reach a
compromise? Surely we can find something that we can both accept?

_______________________________________________
Frugalware-devel mailing list
[email protected]
http://frugalware.org/mailman/listinfo/frugalware-devel

Reply via email to