Subject | RE: source control - marion etc |
---|---|
Author | David Schnepper |
Post date | 2000-01-26T05:32:20Z |
I think there was an overfocus on marion's shortcomings.
Marion's best feature (2nd best being using IB) is the change history
it keeps. There has been innumerable times I used that as part of a
bug fixing strategy.
"Ok, here's the buggy code".
"When was it introduced, and why?"
"Does the new fix also fix the original problem".
"What other changes did the same programmer put in about the same
time in other modules that may have the same problem?"
"Where has this buggy code been cloned to? Where was it cloned
from?"
Many change control systems have links to bug tracking systems --
marion's strategy was bit different, and it made it easy to do these
kind of history searches.
As for the main task at hand -- that kinda depends on the where the
bottleneck is for getting 6.0 out the door. If it's going to be
mainly NewCo folk pushing it out, then continuing to use marion may be
the best (short-term) strategy. Changing tools is always a short-term
disruption. (Though, of course, changing to a better tool could
shorten cycles -- "Sharpen the saw").
Dave
-----Original Message-----
From: Doug Chamberlin [mailto:dchamberlin@...]
Sent: Tuesday, January 25, 2000 5:50 PM
To: IBDI@onelist.com; IBDI@onelist.com
Subject: Re: [IBDI] source control - marion etc
From: Doug Chamberlin <dchamberlin@...>
At 1/25/2000 04:31 PM (Tuesday), Dalton Calford wrote:
for
anything other than pure entertainment. Given Reed's list of
shortcomings
of Marion there is only one plausible reason I have heard to continue
using
it - that it uses Interbase as a storage system. Even that reason is
not a
very good one, IMHO.
Shouldn't we focus our attention and energy on the main task at hand,
that
of ensuring that Interbase 6.0 is released promptly and maintained
adequately?
--------------------------- ONElist
Sponsor ----------------------------
Was the salesman clueless? Productopia has the answers.
<a href=" http://clickme.onelist.com/ad/productopiacpc2 ">Click
Here</a>
----------------------------------------------------------------------
--
Community email addresses:
Post message: IBDI@onelist.com
Subscribe: IBDI-subscribe@onelist.com
Unsubscribe: IBDI-unsubscribe@onelist.com
List owner: IBDI-owner@onelist.com
Shortcut URL to this page:
http://www.onelist.com/community/IBDI
[This message contained attachments]
Marion's best feature (2nd best being using IB) is the change history
it keeps. There has been innumerable times I used that as part of a
bug fixing strategy.
"Ok, here's the buggy code".
"When was it introduced, and why?"
"Does the new fix also fix the original problem".
"What other changes did the same programmer put in about the same
time in other modules that may have the same problem?"
"Where has this buggy code been cloned to? Where was it cloned
from?"
Many change control systems have links to bug tracking systems --
marion's strategy was bit different, and it made it easy to do these
kind of history searches.
As for the main task at hand -- that kinda depends on the where the
bottleneck is for getting 6.0 out the door. If it's going to be
mainly NewCo folk pushing it out, then continuing to use marion may be
the best (short-term) strategy. Changing tools is always a short-term
disruption. (Though, of course, changing to a better tool could
shorten cycles -- "Sharpen the saw").
Dave
-----Original Message-----
From: Doug Chamberlin [mailto:dchamberlin@...]
Sent: Tuesday, January 25, 2000 5:50 PM
To: IBDI@onelist.com; IBDI@onelist.com
Subject: Re: [IBDI] source control - marion etc
From: Doug Chamberlin <dchamberlin@...>
At 1/25/2000 04:31 PM (Tuesday), Dalton Calford wrote:
>How much work do you think there would be to update Marion?I'm greatly perplexed by the thought of someone re-inventing the wheel
for
anything other than pure entertainment. Given Reed's list of
shortcomings
of Marion there is only one plausible reason I have heard to continue
using
it - that it uses Interbase as a storage system. Even that reason is
not a
very good one, IMHO.
Shouldn't we focus our attention and energy on the main task at hand,
that
of ensuring that Interbase 6.0 is released promptly and maintained
adequately?
--------------------------- ONElist
Sponsor ----------------------------
Was the salesman clueless? Productopia has the answers.
<a href=" http://clickme.onelist.com/ad/productopiacpc2 ">Click
Here</a>
----------------------------------------------------------------------
--
Community email addresses:
Post message: IBDI@onelist.com
Subscribe: IBDI-subscribe@onelist.com
Unsubscribe: IBDI-unsubscribe@onelist.com
List owner: IBDI-owner@onelist.com
Shortcut URL to this page:
http://www.onelist.com/community/IBDI
[This message contained attachments]