What steps will reproduce the problem?
This has been sub-contentiously bugging me for some time, and recently
surfaced.
The current release is v5.03, supposedly to indicate the a modification to 5.0
The RC3 we have today is v5.3, supposedly to indicate that is is after v5.1 and
v5.2.
But, v5.03 and v5.3 can mean the same number. I thing v5.03 would have been
better named v5.0.3, or v5.0c or something.
Anyway, to fix this, we might name the next public release v5.4, and the
following release (where we tweak the test hardware configuration and test
automation scripts) as v5.5
Original issue reported on code.google.com by prof.bra...@gmail.com on 21 Jan 2013 at 6:15
Original issue reported on code.google.com by
prof.bra...@gmail.com
on 21 Jan 2013 at 6:15