Re: Indiication of new version of source.

Brian, to clarify, the reviewer loaded the source in browse mode so I was
able to open the same source in edit mode and make the changes.

We use Rocket LMi for change management and I have seen the option of using
iProjects but I have used it yet.

Well, I guess I know what I'm doing this weekend.

Thanks for the suggestion,

Rob

On Wed, Jul 24, 2019 at 3:36 PM Brian Parkins <goodprophet.bp@xxxxxxxxx>
wrote:

Rob, I have to ask the question. If the source is already "loaded", (I
assume you mean being edited) on the reviewer machine, how did you
manage to change the source subsequently? (The review download should
have the member locked from update on the server.)

In any case, the situation you describe suggests CMS tooling would be
advantageous. (I can't think of a way that RDi will help, unless you use
iProjects and attempt to save the review copy - it'll then warn you the
server copy has changed.)

Brian.

On 22/07/2019 17:02, Robert Rogerson wrote:

Hi All.
We routinely do code reviews. If the source is already loaded (on the
reviewer machine) and I have modified the source then the reviewer is
looking at outdated source.
Is there anyway in RDi to give an indication that there is a newer

version

of the source that you currently have loaded?

Thanks,

Rob

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com