Thanks guys for the quick responses! Actually my idea was that products that use code names together with version numbering systems tend to get an edge over the other products since people tend to remember code names more than numbers (even though version numbering is there). It's kind of a sub product name used for branding.
For an example: OpenStack: Austin, Bexar, Cactus, ..., Grizzly, Havana Ubuntu: Lucid, Precise, Quantal, Raring Android: Cupcake, Donut, Eclair, ..., Ice Cream Sandwich, Jelly Bean Anyway this just a thought, we could stick with version numbering. Thanks again! On Mon, Aug 19, 2013 at 7:19 AM, Lakmal Warusawithana <[email protected]>wrote: > We have a plan to do frequent releases. Code name does not help that. I > think version number is enough. > > sent from phone > On Aug 18, 2013 9:06 PM, "Deepal jayasinghe" <[email protected]> wrote: > >> Imesh, >> >> Why do you need a code name ? version number does not work ? >> >> Deepal >> >> Hi Devs, >> >> How do you like to give a code name for each major release of Apache >> Stratos? >> >> I'm not sure whether this is too early to discuss since we are still in >> incubation. >> >> Thanks, >> >> -- >> *Imesh Gunaratne* >> Technical Lead >> WSO2 Inc | http://wso2.com >> Mobile: +94 77 374 2057 >> Blog: http://imesh.gunaratne.org >> >> Lean . Enterprise . Middleware >> >> >> -- *Imesh Gunaratne* Technical Lead WSO2 Inc | http://wso2.com Mobile: +94 77 374 2057 Blog: http://imesh.gunaratne.org Lean . Enterprise . Middleware
