That's a funny number!

[Enjay]

In keeping with the transfer of the ZDoom and GZDoom source from SVN to Git, the file naming conventions for those two builds have changed. As of now, the archives containing the builds will use the generated revision numbers. These numbers are not very catchy (e.g. the current GZDoom one is G1.9pre-38-g0980f66) but it is the way that the numbering is done and it shows exactly which commit of the source the build was based on.

If you are reporting bugs for these builds in either the ZDoom or GZDoom forums, please remember to state clearly the revision number for the build where you experience the problem. The revision is recorded at the top of the ini file like this:

Code: Select all

# This file was generated by GZDoom G1.9pre-38-g0980f66 on Mon Jun 24 17:25:30 2013

So you can open that to copy/paste the number into your bug report. The ini file is usually in the same folder as the executable but if you can't find it, you can use the "whereisini" console command to tell you where the file is.

[Enjay]

I've been thinking about the frequency of making builds and, particularly during periods of rapid updating, I have been making a lot of builds and uploading them. It strikes me that this probably isn't necessary and it does eat into my time quite a bit. I've also noticed that Randy and Graf do most of their commits to the repository over the weekend (which makes sense given that ZDoom and GZDoom are hobby projects).

As a result, I intend to alter when I do the builds from "any time I spot there has been a update" to "Mondays". ie, assuming that there have been updates over the previous week, I will make and upload a new build at some point on Monday. I will, however, remain vigilant and if there are any particularly important mid-week updates (important bug fixes or significant new features) I will make a build accordingly. Similarly, if there is a feature that someone simply can't wait a few days for, they can fire a request in my direction and I may even make a build.

[Rachael]

I've been thinking about the frequency of making builds and, particularly during periods of rapid updating, I have been making a lot of builds and uploading them. It strikes me that this probably isn't necessary and it does eat into my time quite a bit. I've also noticed that Randy and Graf do most of their commits to the repository over the weekend (which makes sense given that ZDoom and GZDoom are hobby projects).

As a result, I intend to alter when I do the builds from "any time I spot there has been a update" to "Mondays". ie, assuming that there have been updates over the previous week, I will make and upload a new build at some point on Monday. I will, however, remain vigilant and if there are any particularly important mid-week updates (important bug fixes or significant new features) I will make a build accordingly. Similarly, if there is a feature that someone simply can't wait a few days for, they can fire a request in my direction and I may even make a build.

That sounds fine, Enjay, nothing here is worth stressing over and it would be unfair to expect you to spend all your time making a number of builds that it would be quite likely no one would use.

[Enjay]

Good news.

(As Eruanna now knows), Blzut3 has stepped up and offered to make ZDoom and GZDoom builds party of his automated nightly build system. So there should now be a nice, regular build update system for ZDoom and GZDoom Windows binaries with the builds hosted in the usual place. A big thank you goes to Blzut3 for making this happen.

[Blue Shadow]

So, you're not going to be uploading builds anymore?

[Enjay]

Correct. Blzut3's automagical system will do it. I'll just be keeping an eye on the site and clearing out old/redundant files. I'll probably still keep my own copies of the Git repositories around and build stuff for myself just out of interest and for practice. If, for some reason that I can't currently think of, one of my builds needs to be uploaded, I'll do that.