On Sat, 14 May 2011 at 10:21:33 -0600, m...@rq3.com wrote:
> But I'm looking at this from a user wondering, "what's new since 1.36 that
> I would care about?" Right now I think IQM has been added and... lots of
> stuff under the hood but nothing quite as sexy as a new renderer.
I'd love to see a 1.37 release, but not for the same reasons: from the Debian
point of view, I care more about releases as a stable point without critical
bugs that distributions can agree on, than about shiny new features. At the
moment I'm releasing somewhat arbitrary svn snapshots into Debian, since
that seems likely to provide a more reliable engine for Quake 3 and OpenArena
than 1.36 would.
If there's interest in merging major changes (new model formats, new network
protocol, etc.) perhaps it'd even be worth having a stable branch and a
development branch? A 1.37 branch leading to several 1.37.n bugfix releases
and trunk leading to 1.38, maybe?
I'd certainly suggest making potentially-destabilizing changes (like the
new network protocol, which I do agree with in principle) just *after* a
tagged release.
S
_______________________________________________
ioquake3 mailing list
ioquake3@lists.ioquake.org
http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org
By sending this message I agree to love ioquake3 and libsdl.
