5.0 and or 4.8 (was Re: [development] Drupal x.x.0 freeze date)

[Robert Douglass]

How 'bout naming them for some city where we had an important conference 
that year? So 4.7 could've been Amsterdam or Vancouver. 4.8 could be 
Brussels.

-Robert

Khalid B wrote:
> Codenames are used all over the place.
>
> Intel has it for the CPUs (Dothan, Willamette, Prescott)
> Apple has it for OS (Panther, Tiger)
> Microsoft (Chicago, Longhorn)
>
> The only drawback I see from using it is that if some documentation
> refers to the code name, and then the release number comes along,
> and there is a disconnect.
>
> We can avoid that by using both in the future, for example the release
> 4.8 becomes (4.8 Dreamy Druplicon) release, so there is no confusion.
> Debian and Ubuntu use that scheme, and it works OK me thinks.
>
> Oh, and Dreamy/Droopy/Drooly are bad names, and can be a turn off
> for some prospective users, so let us keep the code  names simple
> and neutral,  if we decide to use them (fish names, car names, bird
> names, city names, ...etc.)
>
> What are the other objections to code names.
>
> On 4/30/06, Karoly Negyesi <karoly at negyesi.net> wrote:
>> > How about using a code name for the next release and not just a 
>> number?
>>
>> Dries does not like code names, but now that someone else raised the
>> point, I will add my two cents.
>>
>> Let's call it CRYSTAL: Come, Release Years Sooner Than Able Last! 
>> (Sorry,
>> could not resist.)
>>
>