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

[Khalid B]

The best scheme is a meaningless name picked from a virtually endless
"domain".

Using Vancouver or Amsterdam because we had a conference there means
that we will be in trouble next year if the conference is held in the same city.

This is the same way you name machines in a network. Never give the machines
meaningful names or structured code/numbers that may change on upgrades,
relocations, mergers/acquisitions, ...etc. (An example was in the early days of
Usenet and  email, machines were called by the make/model, e.g. decvax or sun,
and then they were  replaced but the name has to stay the same).

We can call them Ferrari, Porsche, ...etc.  (Dries will like these). We can
call them Eagle, Hawk, Falcon,  or Shark, Orca, Stingray, ...etc.

This is not to  say that it can have hidden messages or dual meaning (I am
sure chx can invent a witty acronym out of any of those).

>From the exotic ideas departments, we can name the upcoming one HoneyMoon
because Dries got married earlier this year. Or, we can use my
youngest daughter's
name, or someone's favorite pet. The supply is endless.

Before we decide on a code name, let Dries bless the idea of using code names
first,  since he had reservations in the past (as per chx). I think it
solves the issue
of us being stuck with a number and over (or under) growing it in the
release cycle.

On 4/30/06, Robert Douglass <r.douglass at onlinehome.de> wrote:
> 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.)
> >>
> >
>
>