Version number changes

[Megiddo]

As Stickly Man mentioned in the other thread, we have changed version numbering for betas.

Betas are now "backward-looking" numbered. This makes it a little easier to keep track of what someone's using from their version information.
"v2.31" -- Release version
"v2.31w" -- Release version downloaded from workshop
"v2.31d (some date)" -- The release version above, WITH additional (beta) modifications on top. The only source of this should be GitHub. The date is the UTC date the code was committed.
"v2.31d" -- The release version, WITH beta mods. But for some reason, the build information was removed so we can't pull a date. Hopefully we never see this, but here it is just in case.

This change is live in the new repo. We will be checking for newer updates and notifying admins in the future.

[JamminR]

Strongly suggest we add a "ulx version" command, and an XGUI text box (about tab?) to just copy from, so folks don't keep having to post pictures of their XGUI screens that don't always show all of what we need at the bottom.
Besides ULib and ULX versions of course, perhaps it could show versions from our other releases that people have installed.
I know debuginfo includes both, but, just a version command would be swell too for beginning troubleshooting an issue.
Perhaps add a global table for any other ulib/ulx compatible addons to tie versions into.

[Megiddo]

The version is at the bottom of ulx help -- think we need a ulx version command too?

What do you mean regarding the global table? We have ulx.getVersion and ULib.getVersion which returns version/build/workshop information. Is that what you mean?

[JamminR]

Yes, too, some sort of command, and perhaps xgui window popup or something, to return all important version information that can easily be copied into a forum post when we ask them to verify what version they are using.
Because;
1) if we continue to use a 'stable release' method stored on a http server, in combo with 2 other release methods
2) other idiots decide to release ULX/ULib through their own means/own sites/own zips for server packs
people will continue to get old versions.
Giving them a single place to copy / paste will make it easier on us to tell them they need to get version <x> from <whatever method>
I don't know how many times people go and post a screenshot of the bottom of XGUI because that's the only place they know to do.

As for the .getVersion commands, somewhat. But I mean more along the lines of being module (ulx OR Ulib) friendly.
So our new version command would show not only possibly ANY module we released (utime/uban/uclip/...) stored in the table, some function or table insert could add another devs custom addon.
So if someone ran (hypothetical) "ulx version",
Return text (stored table or other means)
ULib v x.xxW
ULX v x.xxW
Utime v x.xx date
Someones Custom ulib mod#1 v x.xx
Someones Custom ulx mod#1 v x.xx

[Megiddo]

Yes, too, some sort of command, and perhaps xgui window popup or something, to return all important version information that can easily be copied into a forum post when we ask them to verify what version they are using.
Because;
1) if we continue to use a 'stable release' method stored on a http server, in combo with 2 other release methods
2) other idiots decide to release ULX/ULib through their own means/own sites/own zips for server packs
people will continue to get old versions.
Giving them a single place to copy / paste will make it easier on us to tell them they need to get version <x> from <whatever method>
I don't know how many times people go and post a screenshot of the bottom of XGUI because that's the only place they know to do.

As for the .getVersion commands, somewhat. But I mean more along the lines of being module (ulx OR Ulib) friendly.
So our new version command would show not only possibly ANY module we released (utime/uban/uclip/...) stored in the table, some function or table insert could add another devs custom addon.
So if someone ran (hypothetical) "ulx version",
Return text (stored table or other means)
ULib v x.xxW
ULX v x.xxW
Utime v x.xx date
Someones Custom ulib mod#1 v x.xx
Someones Custom ulx mod#1 v x.xx

That's a great idea on incorporating version information from other addons! I will add it to the list for ULX4 (we are making progress on it, maybe it's not a pipe dream?). But, the system we've setup is very easy to make generic to any addon. I imagine most mod authors will love getting the automatic update notices to their users from using ULX. (And of course, we'll allow them to opt-out if they choose.)

I will, however, add "ulx version" to ulx 3.x which will return ULib and ULX's version data.