[Gtkradiant] mo' bullshit

[ydnar]

Perhaps a remote installer that people could run to update their GtkRadiant
installs, with the option of preserving older builds.

The package size alone I think is another reason people have been shying off
recent builds. As it is now, myself and others have been recommending people
download the full 1.2.1, install that, then patch with 1.2.6-nightly. This
is not a small endeavour for those with dialup connections (and/or a BT
drop-every-two-hours line).

If not a remote installer, perhaps just segmenting the installs into "game
packs" and "binaries" would do the trick. The map
media/models/shaders/textures/help files/plugins that accompany the full
install have a slower/different update track. Perhaps the packages should
reflect this.

Is there Win32 RPM or something equivalent that could be built, so people
could tick off the options they desire before download/install?

y


----- Original Message -----
From: "Timothee Besset" <ttimo@idsoftware.com>
To: <gtkradiant@zerowing.idsoftware.com>
Sent: Thursday, March 28, 2002 1:16 AM
Subject: [Gtkradiant] mo' bullshit


> I think a bunch of people here have already read through this:
> http://web.lemuria.org/q3tc/scoop/story/2002/3/27/203129/125
>
> We are pretty used to that kind of rant, it's not really a problem
> anymore. However it seems it's that time of the year were we are going to
> need to explain the usual things about Radiant again, how it evolves,
> where does it come from, how QA happens in an open source project etc.
>
> With the advent of HL/CS support and more multiple games support (who said
> JKII?), QA is going to become even more tricky, and we're gonna get even
> more public exposure (specially to newbies), so I say we should expect to
> see more and more of that.
>
> I feel that there is one true problem though in the way the releases have
> been evolving. Stable release / nightly updates and stuff .. isn't that
> clear anymore .. even for me. We came from a situation were we had 1.1 or
> 1.1-TA as the stable release, and 1.2 were only nightly releases. At that
> time, nightlies were truly beta quality, and we recommended 1.1* as the
> production editor.
>
> Now we have completely shifted focus. There is no build of 1.3 available
> at this time, and the 1.2 nightlies are actually stable updates over the
> last 1.2.3 stable release. I still want to call them nightlies because
> they are meant as 'release often' and 'small updates over existing
> install'. And I won't call them beta either, because they truly are stable
> updates over something we already tagged as 'stable'.
>
> We did such a good job telling people that nightlies were experimental
> when we first introduced them, that they haven't recovered yet and are
> reluctant to use 1.2.6
>
> I'm not sure what kind of action we should take. Could just post on
> qeradiant.com with some more explanations. But I think a more definitive
> page on the website may be good. Some kind of manifest, explaining how the
> QA is done, how the releases are handled and stuff.
>
> feedback welcome obviously :)
>
> TTimo
>
> _______________________________________________
> Gtkradiant mailing list
> Gtkradiant@zerowing.idsoftware.com
> http://zerowing.idsoftware.com/mailman/listinfo/gtkradiant
>