----- Original Message ----- From: "Geer, Christopher S" <[EMAIL PROTECTED]>
> The bottom line is the container coding > has already begun Where is it? > and is under way but if we go down this path of > "starting over" (I know probably not the right term) then we have to > first look at the framework and make sure it meets the needs for a > componentized container, which I'm not sure it does right now. Right now > the framework interfaces are in flux, which in turn affects the > container so we need to nail down the framework before the container can > really be stable. I already say that I prefer small deliveries, small evolution of code. I thought that interfaces were already defined (at least the minimum set) and the first Avalon# container could be uploaded to CVS. > Something I'd like to see done is just start developing a list of > capabilities that we should meet. Now I agree with Berin's XP approach > concepts that say you shouldn't have "hard and fast" requirements but a > living set of capabilities is a good idea so it can foster a "common > goal" in the team. I still believe that we should find a way to post > these to some website (that is up-to-date) as we agree on them for > historical purposes unless we just continually post updated sets to the > list over and over again. Agree. This list should be done by Berin while he have the big picture. hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
