Comment 5 for bug 628846

I know nothing about software builds so these comments may be completely useless. http://StackOverflow.com has interesting questions and often interesting answers. Problems related to propagating version numbers seems to be common so there seems to be more than a few answers with coded scripts but the specific one you would need would be dependent on what software is used for the build. I did a search on StackOverflow for +update +version +number +build. The plus sign is needed because the default search puts an OR between each term.
http://stackoverflow.com/search?q=%2Bupdate+%2Bversion+%2Bnumber+%2Bbuild

If four field version numbers were not a problem in 0.47.x.x then they won't be a problem in 0.48 but some Windows installers seem to ignore the fourth field so 0.48.0.1 would be the same as 0.48.0.2. But this likely does not matter to end users because by the time something is released to the public the version will be at least 0.48.1.
http://msdn.microsoft.com/en-us/library/aa370859%28v=VS.85%29.aspx