Release engineering confusion
Steve Bertrand
iaccounts at ibctech.ca
Thu Nov 17 00:59:57 GMT 2005
> >>>>> In production (at an ISP), what is the best to
> >>>> follow...RELENGX_X or
> >>>>> RELENG_X? I have 4.x, 5.x boxes in production, and this
> >> 6.x box is
> >>>>> being prepared for the same.
> >>>>
> >>>> See the Handbook:
> >>>>
> >>>> 20.2.2.2 Who Needs FreeBSD-STABLE?
> >>>
> >>> Thank you. However, that entire page out of the handbook
> >> pretty much
> >>> clarifies that a production environment should *not* track either
> >>> STABLE or CURRENT.
> >>>
> >>> So I'm assuming I'm best off with RELENG_6_0 etc, etc?
> Does anyone
> >>> here actually run STABLE or CURRENT in a production
> >> environment? I've
> >>> personally had the most luck with RELENG_4 which is still
> >> my main box,
> >>> but now my curiosity has got the best of me.
> >>
> >>
> >> I generally track -RELEASE but my production boxes are
> currently at
> >> 5.4-STABLE from a while ago since there was an issue I was
> trying to
> >> fix and was hoping someone had put a patch in to fix whatever my
> >> issue was :-) My issue has not shown up since and my
> boxes have been
> >> working fine.
> >>
> >> But in general I play it conservative and track -RELEASE
> >
> > Thanks Chad,
> >
> > Do you 'sup and build in a devel lab first, or do you perform your
> > upgrades in real-time, and if something fails go from there?
>
> Major version changes I try and do in a lab first and make
> sure all is good. -RELEASE patch levels I do live and have
> never had an issue. The current switch to -STABLE was also
> live since I was in a bind trying to figure out why I was
> getting a hanging machine...
Thanks again. So, essentially, it's ok for me to track a release...any
release and feel confident that I am secure (at least up to date as I
can be) without introducing new *feature* bugs into a live environment?
Realistically, that's exactly what answer I've been looking for.
My systems perform very particular tasks. I don't need anything new, I
just want to ensure I've got all the sec/bug patches that our fine
fellows have produced, and we know are stable (not as in FBSD-STABLE). I
don't have the time, nor staff resources to test every single update in
a lab before we deploy, hence the reason for this whole entire thread.
Steve
More information about the freebsd-questions
mailing list