dantarbill
Uh...What happened to the 'O'?
 
2016.03 doesn't start with 'O'.
 
Is there some little burg in Massachusetts named 2016.03?

So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Andrew Rossa [Cakewalk]
So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Thank god.

Andrew Rossa [Cakewalk]

dantarbill
Uh...What happened to the 'O'?
 
2016.03 doesn't start with 'O'.
 
Is there some little burg in Massachusetts named 2016.03?

So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Thanks for the decoder ring.  (I'm pretty sure the scheme was self evident though.)
 
But...where's the fun in that?  How are we now going to ponder and speculate about what the next release name is going to be?
 
This Guy: Hey...I bet it's going to be 2016.04.
That Guy: Naw...that's crazy talk!
Other Guy: I'm voting for 1812.Overture
 
(How disappointingly corporate and completely sensical.)

Andrew Rossa [Cakewalk]

dantarbill
Uh...What happened to the 'O'?
 
2016.03 doesn't start with 'O'.
 
Is there some little burg in Massachusetts named 2016.03?

So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Hold on here. What if you're in a country that starts numbering months from zero? This numbering scheme may require some rethinking. 
 
Yeah, I don't miss sitting in on requirements meetings at all. 

dantarbill

Andrew Rossa [Cakewalk]

dantarbill
Uh...What happened to the 'O'?
 
2016.03 doesn't start with 'O'.
 
Is there some little burg in Massachusetts named 2016.03?

So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Thanks for the decoder ring.  (I'm pretty sure the scheme was self evident though.)
 
But...where's the fun in that?  How are we now going to ponder and speculate about what the next release name is going to be?
 
This Guy: Hey...I bet it's going to be 2016.04.
That Guy: Naw...that's crazy talk!
Other Guy: I'm voting for 1812.Overture
 
(How disappointingly corporate and completely sensical.)

HAHA. Yeah I know. But you have to admit it is simpler to understand. 

In fairness, Andrew did not claim the release identifier would always correspond to the year and month of the release just that the first part of the identifier is a year, the second is a month and they happen to coincide for this release and the next one.

kevinwal
 
 
Hold on here. What if you're in a country that starts numbering months from zero? This numbering scheme may require some rethinking. 
 
Yeah, I don't miss sitting in on requirements meetings at all. 

Or another planet in another galaxy far far far far away? with no concept of months in a solar cycle?

This is really going to screw things up for me when I retire to Mars. Even the astronomers can't agree on whether a Martian month is 56 sols, 42 sols, or something else altogether. However quite a few Martian calendars distribute the year over 24 months, which allows Cakewalk to include a convenient disclaimer of "innovation delivered monthly (except on Mars, when it's bi-monthly)." But then there's the confusion of when bi-monthly means twice a month vs. when it means every two months...never mind, just make the update available when you can.

Hey guys, it could be worse.  It could be 03.2016

Andrew Rossa [Cakewalk]

dantarbill

Andrew Rossa [Cakewalk]

dantarbill
Uh...What happened to the 'O'?
 
2016.03 doesn't start with 'O'.
 
Is there some little burg in Massachusetts named 2016.03?

So we moved to a more conventional naming method as to offer better clarity. Here's a decoder for it.
 
First four digits = year (in this case it 2016)
Last two digits = month # (in this case month 03 for March)
 
So moving forward if you have a question about a release, you don't have to go back and try to figure out what city came in what month. Instead, you just refer to it by year and month. So if you want to ask a question about the April 2016 release, it would 2016.04. 

Thanks for the decoder ring.  (I'm pretty sure the scheme was self evident though.)
 
But...where's the fun in that?  How are we now going to ponder and speculate about what the next release name is going to be?
 
This Guy: Hey...I bet it's going to be 2016.04.
That Guy: Naw...that's crazy talk!
Other Guy: I'm voting for 1812.Overture
 (How disappointingly corporate and completely sensical.)

HAHA. Yeah I know. But you have to admit it is simpler to understand. 

MUCH SIMPLER!
Will any extra updated/patch be termed as 2016.03.16 - if that is released on 16th, or it will be 2016.03.01
 
Thanks
Snehankur