To prepare our users for a smoother migration from Fortress to Merlin as we get nearer to that time period, how about we decide on a name for the Container, and have our current container projects act as code names.
Why? Well the internal architectures of Fortress and Merlin are conceptually the same, but internally very different. If we say that we are releasing Fortress, and then we say that Fortress is gone and now we are releasing Merlin, then in the public perception we will alienate our users. If we say that we are releasing Excalibur Container (to separate it from Phoenix), and this release is codenamed "Fortress", then when we release Merlin there won't be the kickback. All we are doing in the public perception is releasing new versions of "Excalibur Container". This release happens to be codenamed "Fortress", and next release is codenamed "Merlin"--but essentially perceived as one product. This will help prepare the mindset so that when we build UberContainer (AKA Avalon Container) it is the resultant merge of Fortress, Merlin, Phoenix, and Tweety. While internally the projects are very different, the outside front we are presenting is one. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
