Comments on: A Little About Code Names

By: Stephen Stagg

Stephen Stagg — Tue, 25 Mar 2008 01:53:15 +0000

I was thinking about something similar a recently, my solution tends to be just to overwrite old code with newer revisions. Of course, this sucks bigtime, but it does stop me from accidentally using stale code.

The solution, of course, is to have some form of Revision Control System, like svn or similar. That way, if you tag properly, you can keep all copies of a design/code AND have relevant tags, AND have datestamps.

Of course, I haven't found a windows/windows IDE friendly RCS system yet. so confusion still reigns.

I was playing about with the idea of coding a webpackage system, whereby an entire website was encapsulated in one file, and revision controlled internally, but I don't know if I will take it forward yet.

By: Adam S

Adam S — Mon, 24 Mar 2008 23:33:22 +0000

Interesting! I like knowing the background of codenames and I like when they follow some sort of theme. I also happen to agree that “Aloha” is a good first release name, it sounds powerful and has a good connotation.

By: Thom Holwerda

Thom Holwerda — Mon, 24 Mar 2008 13:19:21 +0000

Very funny you should bring this up, as a few weeks ago, we had a very entertaining discussion in #haiku about the code name for the Haiku r1 release project. In the BeOS world, codenames were awarded to an entire alpha/beta/rc/final release cycle (so not to just individual alpha or beta releases). For BeOS, codenames were taken from a TV series called “Hawaii 5-0″, which explains names like Maui, Dano, and so on.

We found out there actually is a town called Haiku (!) on the Maui island (what are the odds??), so we might settle on a town down the road to Haiku. Another option, an option which I personally really like, is calling Haiku r1 “Aloha”, a codename supposedly reserved for a future BeOS release or another Be product (aloha.be.com existed). Would be fitting, the first release, named Aloha.

Interesting in ay case :).