Contributed by jose on from the bug-hunters dept.
... the main issue we have is actually _running_ the packages that are produced, because that is the only way to run into eventual problems. It is important that the community helps here, since the number of packages is huge, and discovering the problems that surely lurk is important!Now's as good a time as any to upgrade to -current (which is pretty stable in most regards for a development box) and try out the new packages. If you can, use a freshly installed box and when you find a bug, notify the maintainer.
(Comments are closed)
By Anonymous Coward () on
Thanks.
Comments
By Anonymous Coward () on
By Anonymous Coward () on
By Anonymous Coward () on
(It's a broken software but that is another story)
By Anonymous Coward () on
Comments
By Anonymous Coward () on
Compiling current is a different story, I almost never compiled anything, just installed snapshots. And further, I just tried installing the latest snapshot this afternoon in the last hour at work. On a Dell 266 pentium 3, it installed flawlessly and I left on time. Tomorrow I'll test some packages.
So if you have a machine to spare, go for it. You will grow from the experience. On the other hand, I now have to be a little more careful with the production servers, so I have stable compiled and installed on the 10 or so. Management is a little more sensitive to downtime, so I use a test machine for new versions.
Comments
By Anonymous Coward () on
I guess every time I've reviewed the "upgrade to current" faq, all the extra things needed that might have changed structurally (new users/groups, /etc changes, and so on) since the last release seemed somewhat daunting, and that I would probably miss stuff :)
By jose () on http://monkey.org/~jose/
the process was rather painless, and i'm working on improving my automated update methods. it feels good to have a fully updated system though ... probably ok for devel boxes, but boxes which need to be reliable i wouldn't move to -current quite yet. it still has a few kinks lurking around.
as for "what's broken?" we know some of what's broken, but much of it we don't. we need to find those subtle bugs. looks like a double free cropped up in a command somewhere, hopefully we can isolate it and whack it. stuff like that. like i said, just upgrade if you can, give your system a good thorough use and keep an eye out for bugs.
By jaeger () nshinobi@yahoo.com on mailto:nshinobi@yahoo.com
so this package needs to be looked at tis broken
also any chance that the sound effects pluggins could be included in the next package release for 3.3.............
jaeger
Comments
By jose () on