Codenames for versions / builds
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
My projects all start with code names, and I use US Military Aircraft names - Falcon, Eagle, Blackhawk, etc
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
You forgot: 1.0.380.0 "Airbus" btw... what a nice plane, specially the upper deck (and its bar)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
Yeah - well when it tries to land or take off it will often find an out-of-runway error.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
I name them after that TV show where they battle aliens on earth, You know, V 1.0, V 2.1, &etc.
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein
"If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
I worked at a place where all the project managers used code names and everyone else used the actual product name and release version. Where it got even more confusing is that the project managers would assign code names to sub-projects which overlapped their other code names, which would sometimes change if they drifted out-of-sync "too much" with the parent project. The end result was sometimes quite comical: Dev at standup: I'm working on X. PM: No, you're working on Y. Lead: What's Y? PM: X, but for D instead of C. Everyone: What's D? PM: The name for 1.24.1 And on and on....
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
Due to the way my product management works, my software tends to have many small iterations. Coming up with codenames for those would put an ununderestimatable load on the programmer.
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
I usually use "Fuuukd up patch 1 of even worse release by that moron sitting in cubicle opposite to me"
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
-
i have had to start using a logarithmic numbering system. it used to be prime numbers, but had too many complaints from colleagues that they could not figure out the next version number after 13.
Just a side note on the 737... I don't think there is anything quite as remarkable as how a French pilot can make one of those birds climb taking off out of Paris! Truly an experience that I will never forget!
-
Do you have codenames for your builds / versions? I usually don't but could resist naming release 1.0.737.0 "Boeing" :)
-
Susie. Actually I call most of my projects Susie.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a fucking golf cart.
"I don't know, extraterrestrial?" "You mean like from space?" "No, from Canada." If software development were a circus, we would all be the clowns.Yup ... Sue Zuki, Sue Baru, Sue Nommy