Re: Source/object mis-match

["Dare @ Work" <oludare@xxxxxxxxxxxxx>]

I will assume that your Turnover Admin is not doing his/her job right.

----- Original Message -----
From: "Richard Reeve" <richreeve@yahoo.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, February 05, 2002 4:04 PM
Subject: Re: Source/object mis-match


> --
> [ Picked text/plain from multipart/alternative ]
>
>  In fact, turnover is in use here.  I'm not sure why a mis-match is
suspected.
>   "Dare @ Work" <oludare@ix.netcom.com> wrote: You need a good change
management apps like Turnover.
>
> ----- Original Message -----
> From:
> To:
> Sent: Tuesday, February 05, 2002 3:56 PM
> Subject: Re: Source/object mis-match
>
>
> > You might ask if anyone knows about the site's programming standards &
if
> > they have been followed religiously. Do you have some document some
place
> > that spells out any such rules?
> >
> > I use QDOCSRC for the purpose of telling PROGRAMMERS what's going on &
> > something in the generic BPCSDOC for a larger audience. The first
> document
> > in our QDOCSRC is A_READ_ME with purpose statement & navigation guidance
> to
> > all the documents.
> >
> > Example: I develop something in the TEST library, we do some tests, the
> > results are real good but we want to tweak it a bit more before going
> live,
> > then after a while everyone is pleased.
> >
> > Now we could copy the execution objects from TEST to LIVE, but I do not
> like
> > that approach because 6 months later there is a request from someone to
do
> > another modification & thanks to PDM-54 I can see that the version in
TEST
> > source has stuff not in the LIVE source but I cannot remember if the
TEST
> > work was something we abandoned or if it was something implemented.
> >
> > The way I prefer is to rename the LIVE source with some letter appended
as
> a
> > backup just in case of the old good source, then copy the TEST source to
> LIVE
> > & recompile it in LIVE, so that the TEST version, if we hang on to it,
is
> in
> > sync with the LIVE version.
> >
> > If your shop has had multiple cooks, it is possible that different
people
> > have been handling this different ways, so you not have a consistent
story
> > with object management.
> >
> > MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
> ---------------------------------
> Do You Yahoo!?
> Send FREE Valentine eCards with Yahoo! Greetings!
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>