Steve,
> > Actually, Noel's last email raises a bigger question for me... what
Avalon
> > **release** are we proposing upgrading to? I would be *much* more
> > relunctant if the proposal is just to upgrade to Avalon's HEAD. What
we're
> > running with now was HEAD at one point, and then things start changing
and
> > we're told we have an unsupported version.
>
> > If Avalon has a release we want to upgrade to, that sounds great. But
just
> > upgrading to their HEAD sounds like trouble in river city to me.
> A combination of both.
> 1. build against specific version of jars with crear version
> dependencies and release status
> 2. gump validation against the CVS HEAD
Serge's point is really valid though. THIS time we have to get release
jars, with all of what that entails (including tagging the CVS). As you've
noticed, you can't even backup to what we have without guessing about some
old beta version of cornerstone.
Yes, GUMP will build us against the Avalon CVS HEAD, but that's just an
Early Warning System to get us running over to avalon-dev@ to see WTF is
going on.
Is the Avalon PMC able to define a coordinated Release of all the A4 modules
such that we know that they all work together?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
