Le Tue, 17 Jan 2012 09:56:54 -0800 (PST), James Buren <[email protected]> a écrit :
> Fine. I can make a new WIP called basetesting after 1.6. This is something I > don't wish to deal with until then. The WIP will contain most changes to > items in base group. The only ones that should just be done in current are > ones that won't bring the whole system to a screeching halt if something goes > wrong. An example of some that would be fine in current base would be typical > ones that usually cause no problems, such as minor kernel bumps, rebuilds of > the initrd, or tools that are not mission critical. > > _______________________________________________ > Frugalware-devel mailing list > [email protected] > http://frugalware.org/mailman/listinfo/frugalware-devel Hi I'm not agreed with that when I see the breakage into current. My wifi don't work, some services not started ... Now I should enable systemd debug for check the broken services (module are not loaded...) For me all packages bumped into base are critical even a kernel minor bump. You should rebuild modules, initrd... or that say we bump without tested and it's not acceptable for me. In the real life (at work) you can't do it why we can do it with frugalware ? And I will repeat "ALL" packages into base are sensitives and should have a minimum test before bump it into current. I will don't debug my box(s) every time we bump some base packages!!! All base packages should be bumped into a wip before. The users are not beta testers BTW can you add pkgrel++ to kernel-initrd for users don't crash on reboot. thanks Bouleetbil _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
