Good point Cheng,

But, IMHO, code names add some excitement about a release, maybe being more conservative about code names, and apply a single code name in the entire release cyle, I mean, the first alpha has the code name wildfly (the same name of the project), so keep that code name to the Final release, alpha 2, beta 1, beta 2, rc1 .... all of them should be "wildfly", It comes to my mind Ubuntu, for every release during the development phase there is a code name, and the final release it's simply called "Ubuntu XX.XX".

Jorge Solórzano
http://www.jorsol.com

On Wed, May 22, 2013 at 8:41 AM, Cheng Fang <cfang@redhat.com> wrote:

I would avoid any code name and prefer using the plain old project name
+ release version.

Having a code name adds another barrier in communication both internally
and externally. Given that it's an open source one, the code name will
inevitably leak into the public and confuse with the same name used in
other products and industries.

Cheng

On 5/21/13 7:44 PM, Jason Greene wrote:
> As you know every release has a codename, and normally it's something we come up with on the day of release, but I'd like to make it more interesting and pick the name at the start of a new release as opposed to at the end.
>
> One name a few of us are quite fond of is "Texugo" but I was thinking of saving that for the Beta or the Final.
>
> Any suggestions?
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev