On Thu, Mar 4, 2010 at 11:58 AM, <and...@msu.edu> wrote: >> But both are related to downtime and data loss. I understand stability >> bugs are likely to pop-up more often with current, and this has been >> my experience. Weird freezes without panic that I did not have with >> release/stabe, and some pf-related panics that went away with recent >> current. >> >> Anyway, I am still not clear where most security bugs are more likely >> to pop-up - in release or current, or either? >> >> Thanks. > > For any established bug thats been around for a while before discovery, > it will be in both -release and -current; established meaning existing > for one more more releases. > > -Current can have bugs that are introduced during the development > cycle. Typcially they are seen fairly quickly and stomped on quickly. > > I've lived on -current on my laptop for 8 years now, and the only time > thats been a problem was rebuilding stuff during a hackathon. If > you use -current, watch the pretty commits flow in, but refrain from > jumping into the new code on your main machine, as I did. Test > machines are of course a great idea.
Thank you! Shouldn't this advice be good for inclusion on the "following current" page on the website? Also how does one find out when it's okay to jump into new code, given that one is a mortal sysadmin - not a C or system hacker who understands which commits could possibly be buggy?
