I get notifications of an update available from Sourceforge but when I look at the About in Otter there does not seem to be any difference from that in the current version. Or am I missing something?
Since it's the development of 0.9.02 I don't think you should expect to see any difference, although perhaps some more info there could be interesting. For instance something like the build date.
The notifications you are getting are most probably related to the release of weeklies (http://sourceforge.net/projects/otter-browser/files/). However many of these weeklies are part of 0.9.02 (second Beta) as the development of a Beta version is an ongoing process (https://github.com/Emdek/otter/issues/milestones).
Also, there is an issue ticket (https://github.com/Emdek/otter/issues/257) on GitHub for the inclusion of date timestamps within Otter itself for identification purposes.
Thanks for the replies.
I was referring to the About window where the build numbers remain the same.
Me too. Like how in Opera it says "Version 12.16 Build 1860." :)
Maybe we could go for manually added version string, appended to "main" version defined already, it could be "weekly #some number" or "beta some number" etc.
Such approach seems to have less disadvantages than automatically generated values and is more flexible.
We could try this today.
Sounds good to me!
Sounds good to me!
I agree - it would be helpful.
@Emdek
Yes, let's have it this way! And did you try it today? It would be nice to see a more elaborate version number in the next turn-of-the-month release.
/me still has the old turn-of-the-month release 0.9.01
@ersi, yes, although defining this text in
.pro file wasn't straightforward. ;-)
OTTER_VERSION_CONTEXT = " weekly $$LITERAL_HASH""30"