Zeal version number in the About Zeal dialog needs to be updated.

[RobertinoValue]

Not a high priority.
The Zeal version number/date in zeal/zeal.pro needs to be updated.
Zeal version 20141123 displays 20140215.

https://github.com/jkozera/zeal/blob/7112812ddc08f0cf06e1a629c739d4e61e28a62e/zeal/zeal.pro#L71

[jkozera]

It's by no means a complete fix, but the recent automated Shippable builds should display correct YYYYMMDD version numbers (they're automatically replaced in https://github.com/jkozera/zeal/blob/master/shippable.yml#L30)

Ideally I guess we should have proper version numbers and perhaps autodetect current one using git tags.

[trollixx]

Closing this as a duplicate of #203.

[RobertinoValue]

How can this be a duplicate of (#)203?
I did not ask to change the version numbering, like was done in (#)203.

I just pointed out that Zeal version 20141123 still displayed 20140215.
Frankly I can't be bothered what type of version numbering is used.

The code I posted was in response to the casual remark/request (last line of his comment) by jkozera.
Besides (#)203 was closed when it showed up in my search results. I didn't open this issue until after lunch from work. Hours later.
I've removed the code to avoid further confusion.

[trollixx]

@RobertinoValue there was no confusion. We need to improve the code, that generates version number. Getting one from the git tags is the best option. So, the proper fix for this issue would be implemented together with #203.

Anyway, we can keep this one open until a new release.

[schlamar]

It's by no means a complete fix, but the recent automated Shippable builds should display correct YYYYMMDD version numbers

Nope, 20150112054614 still shows 20140215.

[schlamar]

This is hard coded in src.pro:

zeal/src/src.pro

Line 21 in 86971e9

DEFINES += ZEAL_VERSION=\\\"20140215\\\"

[trollixx]

Fixed in 022d4be and 8e3d3f0 (for Windows automatic builds).

[RobertinoValue]

Thanks @schlamar.
(Not so duplicate after all.)

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for a related request.