Noel J. Bergman wrote:
What do you mean before compatibility is in place? Are you saying
we cannot move anything until all our dependent projects notify us
and tell us that they are ready?
You cannot depend upon your dependent projects to notify you, period. What
makes you think that more than 1% of Avalon dependents track your CVS or
uses GUMP? It is Avalon's job to maintain compatibility, not theirs to
notify you after things are broken.
To the best of our ability we try to maintain that compatibility--esp.
for released components. Things like GUMP are tools to help in the
process.
If we make a change that is not backwards compatible, it is usually
not intentional.
Can we handle a temporary incompatibility that lasts for a day--or at
the most two?
James as been broken for longer than that now. Ever since the thread
changes. I have posted about that several times. I'm surprised that you
haven't noticed.
The Thread changes are now reverted--however I think your messages got
lost in the deluge of posts.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
