Re: GNUSTEP_CONFIG_FILE value ('/etc/GNUstep/GNUstep.conf') is not an absolute path

[Helge Hess]

On 10. Mrz 2006, at 20:13 Uhr, Jeremy Bettis wrote:
> You can't have every platform tested for every release.

But you need to decide (and declare!) what platforms are actually  
tested prior a release. Otherwise a stable release is pretty useless,  
no?

For GNUstep this means that there needs to be a decision whether it  
supports Windows in releases or not. Which in turn has direct  
consequences on whether this can be a marketing feature or not.  
(don't tell someone that gstep-base works on Windows if a downloaded  
*release* doesn't ...)

> Even for GCC, windows is on the non-critical list.  I am a heavy  
> Mingw user (the only heavy mingw user of gnustep?)  and I don't  
> care if Mingw is tested before every release.  Frankly the idea of  
> someone who never normally uses windows dual booting over to  
> windows once every 3 months to test under mingw before calling the  
> version RELEASE, doesn't really boost my confidence any.

Well, the usual way it works is that you have multiple people  
responsible for reporting on whether a certain state of the source  
(usually the RC, release candidate) works on 'their' platform.
Of course for mingw32 this should not be someone who doesn't use  
Windows ...

More exactly basically every major project doing "stable releases"  
has AT LEAST a beta cycle, usually there is also an RC cycle. GNUstep  
has nothing like that and the 'releases' are nothing more than tagged  
alpha releases.
Not a good base to build upon :-(

BTW: even if you don't want to fix a certain platform support for a  
given release, its much better to know whether a releases does  
support that platform in advance. So that the release announcement  
can be correct ...

Greets,
  Helge
--
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org