Subject | RE: source control - marion etc |
---|---|
Author | Doug Chamberlin |
Post date | 2000-01-26T12:20:43Z |
At 1/26/2000 12:32 AM (Wednesday), David Schnepper wrote:
investment over the next few years should be for the long term health of
the product, now that it is open source. That is, how should NewCo and the
volunteer community invest their efforts over the next year or two?
Focussing on the development and maintenance of the core Interbase product
seems wise. Focusing on the development and maintenance of marion, to add
say branching support, seems foolish if there are perfectly capable
alternatives available.
Short term decisions about how to get 6.0 out the door are a different
matter altogether. Expediency would be more valuable here, especially if
NewCo will be doing 99% of the work.
>As for the main task at hand -- that kinda depends on the where theI see the main task at hand as more long term. I'm thinking about what 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").
investment over the next few years should be for the long term health of
the product, now that it is open source. That is, how should NewCo and the
volunteer community invest their efforts over the next year or two?
Focussing on the development and maintenance of the core Interbase product
seems wise. Focusing on the development and maintenance of marion, to add
say branching support, seems foolish if there are perfectly capable
alternatives available.
Short term decisions about how to get 6.0 out the door are a different
matter altogether. Expediency would be more valuable here, especially if
NewCo will be doing 99% of the work.