"" sometimes, you need to get them to issue another hotfix after the next patch is released because they didn’t incorporate that hotfix into the mainstream patch (has happened to me numerous times) ""
I like this.. it is funny.. but happens.. On Fri, Sep 16, 2011 at 11:17 AM, LJ LongWing <lj.longw...@gmail.com> wrote: > ** > > A hotfix is established when someone discovers a bug in a branch of code, > but can’t wait for the next patch. That user gets the hotfix, ideally, > everyone else gets it in the next patch…sometimes, you need to get them to > issue another hotfix after the next patch is released because they didn’t > incorporate that hotfix into the mainstream patch (has happened to me > numerous times)**** > > ** ** > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *patrick zandi > *Sent:* Friday, September 16, 2011 8:56 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: SRM IMPORT 7.6.04.01 ARERR 191005**** > > ** ** > > ** Found out a few things on this:: > > #1 -- SRM 7.6 needs a Patch to export data properly.. it does not > currently correctly export... > Before you export -- ensure you have this hotfix .. (not 7.6.04.01) > > When does 7.6.04.02 come out ? > > So at what point does a hotfix get sent out -- when you find the problem, > why not put out another Patch to fix this issue instead? > Maybe it is not completed tested.. or there are unique circumstances.. not > sure.. > > > > > > -- > Patrick Zandi > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ **** > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ -- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
