On Wed, Jan 18, 2012 at 2:15 AM, Daniel Exner <[email protected]> wrote: > Hi guys, > > I was only hit minor by udev update: RV770 firmware wasn't loaded, so no > accelerated 3D. ;-) > > I vote against the idea for a wip enforcement on base. Why? > Because a wip makes only sense if its used, and that way the breakages > are found before hitting current. > But as some of you already said, most wip are never used. Or some are > used, but no feedback (whether positive or negative) is given. > Current is used, and the actual breakage showed, that it works: the > experts in fixing it got hit, and it got fixed. > > If ryu0 would have used a wip exactly the same would have happened: he > would have tested it, invite others to do so, no one would have done (or > given feedback) and it would be merged into current.. > > End users using current for production use and complain about breakage.. > naar ;) > > For me a wip makes sense if making a update results in bumping too many > packages, for all mirrors to update them in a reasonable time, or its > visible that an update could have unforseen breakages depending on it. > > Tesing wip repos make only sense if there would be some _automatic_ user > acceptance testing that would ensure no breakages. > Since I've done quite some research in this I can ensure you: this is > currently impossible. > > So, just my 2 cents: _use_ current, fix bugs when possible, have a 2. > box and boot CD for repair at hand ;) > > Greetings > DeX > _______________________________________________ > Frugalware-devel mailing list > [email protected] > http://frugalware.org/mailman/listinfo/frugalware-devel
I'll have to agree with Daniel on this one, a WIP in these case wouldn't be all that useful IMO. If someone bumps something and it's something major which can break things then yes a WIP would probably be nice. But after all it's current, things can break and no one guarantees things work in current ( that's what stable is for ). Of course if you update a package you should build and test it. There would be a solution to current breaking sometimes: use the LiveCD and have some kind of roll-back mechanism to revert the updates. _______________________________________________ Frugalware-devel mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-devel
