Members of the beta team will understand that when I am in the middle of making changes and coming to a testing release point (which can happen a couple times a week, or not for a month or so) I tend to always post multiple builds of the same module version. Because of this and other reasons, I have decided to start using build  numbers when discussing beta builds for a version. In the future, forum 04.0x.0x will be followed by build .17802 or whatever. This will match the assembly version and can help point bug reports to a specific build.
Likewise, while we are always working towards a public release point, we sometimes have to deal with numbers being changed. Therefore, I will follow MS's lead and use codenames for a future public release point. For example, after this release that goes out (4.4.3) I plan on focusing on 4.5. This is not just a bug fix, but if it were I would still say 4.5 and maybe note that it is a service release similar to SP1 (meaning service pack one). In the case of my current plans for 4.5, I know I want to take advantage of some core changes, fix reported bugs from 4.4.3, integrate Ajax and require dnn core 4.5 or greater to run it. Because I am not, nor do I have the time, to be a marketing genius I will simply refer to this release as codename: Ajax.

If anyone has a problem w/ the naming conventions (on the forums beta testing team) please let me know.