GZDoom and ZDoom 2.6.1

[Kate]

Has GZDoom had a release after ZDoom 2.6.1? And if so, can I request a link to the source release? Thanks in advance.

[Blue Shadow]

As far as I know. No, it hasn't.

[Graf Zahl]

No, I was on vacation for most of the last 2 weeks and simply haven't had time to do a new release - which thanks to the current way of doing stuff with a separate branch is not that quick.

[Kate]

That's fine, it's not like it's needed immediately or anything. I was just hoping I could pick up on PyDoom, but whenever you can get around to it is alright with me.

[Ixnatifual]

Cool. Looking forward to it.

[BlueFireZ88]

What's different bout 2.6.1?

[Blue Shadow]

Look here.

[Gez]

Or rather here.

[printz]

The SVN builds of GZDoom are very recent, so I don't know what the kek are you talking about. Aren't they based on ZDoom 2.6.1 by now? Did the GL part get any major enhancements lately that produced those SVN builds? Lol.

[Blue Shadow]

I don't know what the OP's reasons for wanting an offical release version, but some people don't "trust" SVN builds (stability reasnos).

[NeuralStunner]

As far as I can tell: She doesn't update her source fork very often, but an official release is generally a good time to sync to parent. When the fork is based from GZDoom, it becomes entirely relevant.

printz: I think you should take a forum vacation. That wasn't helpful in the slightest.

[printz]

printz: I think you should take a forum vacation. That wasn't helpful in the slightest.

Sorry, I wasn't aware that SVN builds aren't releases . What do the SVN update texts say? If there's any that says 'update to ZDoom 2.6.1's SVN number', then that's the milestone release.

[Gez]

ZDoom 2.6.1 has the particularity that the floatbob changes aren't in it.

[Enjay]

What do the SVN update texts say? If there's any that says 'update to ZDoom 2.6.1's SVN number', then that's the milestone release.

Not sure what you mean by SVN update texts but, as of a little while ago, Randi bumped SVN numbers to 2.6.999. The implication being that the code in the SVN trunk is working towards the next 2.* (presumably 2.7) rather than just being modifications of the previous versions. I *think* that bug fixes to 2.6.0 are intended to be maintenance releases based on the 2.6.0 (now 2.5.1) code rather than the trunk.