On 11/3/05, Hubert Rabago <[EMAIL PROTECTED]> wrote: > What about this. > > Struts 1.3.0 Distro > - struts-core-1.3.0 > - struts-taglib-1.3.0 > - struts-tiles-1.3.0 > - struts-el-1.3.0 > - struts-apps-1.3.0 > - struts-site-1.3.0 > - struts-extras-1.3.0 > > Subprojects can have their own independent release numbers all being > 1.3.0.x, with the "1.3.0" dictated by struts-core. > Once we release struts-core-1.3.1, the other subprojects jump to 1.3.1. > This way it's always clear which distro a none-core subproject release > works with. > (i.e. you can't be sure about using taglib-1.3.1.2 with core-1.3.0, > but you're sure that taglib-1.3.0.4 will work)
I like this. 1.3.1 does not necessarily mean that it has improvements over 1.3.0.15. It just means, that it was retested with 1.3.1 core. But Hubert, seems that your naming convention about Core being _part_ of distro will not fly. P.S. I see nothing wrong with Classic. It calls things what they really are. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
