--- Stas Bekman <[EMAIL PROTECTED]> wrote:
> > Okay, but I want my (quasi-production) environment
> to
> > remain stable and I don't want to expose it to
> > constant patches. This will be even more
> important
> > once 2.0 becomes official. Maybe this doesn't
> really
> > apply to MP, but I also wouldn't want to break any
> > dependencies that other modules have (i.e. MP may
> > require an update to httpd, which breaks something
> > else). (Of course, I wouldn't have this concern
> if I
> > had another system for pure development.)
>
> A properly designed production system, has a
> thorough test suite and a
> staging machine(s), so any new upgrade goes through
> it. You can't just go,
> upgrade the software and hope that it'll work. Any
> new version may
> introduce new bugs, so you are never protected if
> you don't thoroughly
> test *your* system.
>
Agreed. I don't have the luxury of having the
required hardware, so I could not consider this a true
production environment. Hence why I called it
quasi-production; perhaps production-wanna-be would
have been a better term.
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
