[wildfly-dev] Help pick the next release code name

classic Classic list List threaded Threaded
22 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] Help pick the next release code name

Dimitris Andreadis
I think using a codename is good, but it's more practical to associate it with all the
stages of the WF 8.0 release, much like they do in Infinispan, Fedora, Ubuntu, etc. We did
the same in the older JBoss 4.x 5.x releases, too, with the Matrix Theme.

BTW, Diptera is fine, although the WildFly logo comes with 4 wings => Tetraptera, but I
suppose it's a challenge to pronounce? :)

/D

On 23/05/2013 17:41, Jason Greene wrote:

> I'll be honest. It's nothing more than "fun". I see topics like this as a way to build new relationships (or foster existing ones) with all of you who may be thinking about participating in the next release cycle. It's not ultra-important, but maybe it gives someone a small sense of personal attachment or involvement in what we are all working together to achieve.
>
> Now if everyone clamors to kill it, thats fine too. It's up to you guys.
>
> On May 23, 2013, at 12:38 AM, Nicklas Karlsson <[hidden email]> wrote:
>
>> I agree with Jorge in that the release name is mostly a cute marketing thing. "RedHat releases Wildfly 8.0.0.Final (Morning Wood)!".
>>
>> No one even remembers what the previous release was called. I can't personally remember ever using the release name. the customers don't care and internally it's more clear to ask "Did you upgrade your development environment from 7.1.1 to 7.1.2 already" than using release names. But if release names are used, I prefer terms that have a natural order that are clear without googling (i.e insect development vs cyclopes)
>>
>> But on the upside, the project must be going really well if the developers have time to philosophize over the release name! ;-)
>>
>>
>> On Thu, May 23, 2013 at 4:52 AM, Magesh Kumar Bojan <[hidden email]> wrote:
>>> We could go with insect life stages for the code names.  Egg, larva, pupa, adult.
>>
>> Although it makes sense as it is *Wildfly*, better still use the scientific names of insect classification[1]. And if you *ever* run out of code names from that, move on to dinosaur classification and so on ;)
>>
>> [1] http://www.insectidentification.org/insect-taxonomic-orders.asp
>>
>> regards,
>> Magesh
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>>
>> --
>> Nicklas Karlsson, +358 40 5062266
>> Vaakunatie 10 as 7, 20780 Kaarina
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> --
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
>
>
> _______________________________________________
> wildfly-dev mailing list
> [hidden email]
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>

--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dimitris Andreadis
Engineering Manager
JBoss Application Server
by Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx

http://dandreadis.blogspot.com/
_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
Reply | Threaded
Open this post in threaded view
|

Re: [wildfly-dev] Help pick the next release code name

Carlo de Wolf
Then again I bet nobody can find something phonetically offensive with
it. :-)

Carlo

On 05/24/2013 12:14 PM, Dimitris Andreadis wrote:

> I think using a codename is good, but it's more practical to associate it with all the
> stages of the WF 8.0 release, much like they do in Infinispan, Fedora, Ubuntu, etc. We did
> the same in the older JBoss 4.x 5.x releases, too, with the Matrix Theme.
>
> BTW, Diptera is fine, although the WildFly logo comes with 4 wings => Tetraptera, but I
> suppose it's a challenge to pronounce? :)
>
> /D
>
> On 23/05/2013 17:41, Jason Greene wrote:
>> I'll be honest. It's nothing more than "fun". I see topics like this as a way to build new relationships (or foster existing ones) with all of you who may be thinking about participating in the next release cycle. It's not ultra-important, but maybe it gives someone a small sense of personal attachment or involvement in what we are all working together to achieve.
>>
>> Now if everyone clamors to kill it, thats fine too. It's up to you guys.
>>
>> On May 23, 2013, at 12:38 AM, Nicklas Karlsson <[hidden email]> wrote:
>>
>>> I agree with Jorge in that the release name is mostly a cute marketing thing. "RedHat releases Wildfly 8.0.0.Final (Morning Wood)!".
>>>
>>> No one even remembers what the previous release was called. I can't personally remember ever using the release name. the customers don't care and internally it's more clear to ask "Did you upgrade your development environment from 7.1.1 to 7.1.2 already" than using release names. But if release names are used, I prefer terms that have a natural order that are clear without googling (i.e insect development vs cyclopes)
>>>
>>> But on the upside, the project must be going really well if the developers have time to philosophize over the release name! ;-)
>>>
>>>
>>> On Thu, May 23, 2013 at 4:52 AM, Magesh Kumar Bojan <[hidden email]> wrote:
>>>> We could go with insect life stages for the code names.  Egg, larva, pupa, adult.
>>> Although it makes sense as it is *Wildfly*, better still use the scientific names of insect classification[1]. And if you *ever* run out of code names from that, move on to dinosaur classification and so on ;)
>>>
>>> [1] http://www.insectidentification.org/insect-taxonomic-orders.asp
>>>
>>> regards,
>>> Magesh
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>>
>>>
>>>
>>> --
>>> Nicklas Karlsson, +358 40 5062266
>>> Vaakunatie 10 as 7, 20780 Kaarina
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> [hidden email]
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> [hidden email]
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>>

_______________________________________________
wildfly-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/wildfly-dev
12