> So, having at least some system where you run -current, preferably in > conditions similar to production machines, is a good idea to make sure you > don't run into nasty surprises. It also helps us *a lot* as developers to > find out about problems very soon after we introduce them...
good point. i'm kindly new to openbsd, and using the -stable ; will setup a VM to test the updates done in -current, and with luck contribute back with code to the community of this great os. ------------------------------------------------------------- Bcz sex is like hacking.. you get in, you get out, and you hope you didn't leave something behind that can be traced back to you.. ------------------------------------------------------------- http://insanenetworks.blogspot.com ------------------------------------------------------------- On 8 September 2011 18:01, Marc Espie <[email protected]> wrote: > On Thu, Sep 08, 2011 at 01:56:55AM +0200, roberth wrote: >> Seriously, why? > > Funnily enough, a lot of people interpreted that as > "why aren't you running -current on all your machines ?" > > which is obviously a different question, with a legitimate different answer. > > Most specifically, development happens in -current. If things stop working, > and you only run releases, you will only notice when you update to the next > release... > > So, having at least some system where you run -current, preferably in > conditions similar to production machines, is a good idea to make sure you > don't run into nasty surprises. It also helps us *a lot* as developers to > find out about problems very soon after we introduce them...
