[warzone2100-dev] A really awesome way to use git...
Apparently, this is _not_ an April's fool: http://github.com/blog/626-announcing-svn-support They are working on full write support. That should take care of the I-must-use-a-GUI issue with GIT. So if anyone know a way to ensure we do not get line-ending problems, we should be set. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Launchpad: Validate your team's contact email address
Launchpad Email Validator wrote: If you want to make this email address the contact email of 'Warzone 2100 Project', please click on the link below and follow the instructions. https://launchpad.net/token/N4wdzvRLDTDlZMSxX4C0 Did anybody follow this link already? ^^ signature.asc Description: OpenPGP digital signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Launchpad: Validate your team's contact email address
On Tue, Apr 6, 2010 at 1:43 PM, Kreuvf kre...@warzone2100.de wrote: https://launchpad.net/token/N4wdzvRLDTDlZMSxX4C0 Did anybody follow this link already? ^^ Try it and find out ;-) - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1748: ntw bug
#1748: ntw bug
-+--
Reporter: Crymson |Type: bug
Status: new |Priority: major
Milestone: unspecified | Component: other
Version: svn/trunk |Keywords:
Operating_system: All/Non-Specific | Blockedby:
Blocking:|
-+--
{{{
info|11:47:01: [SDL_main] mod_mp (ntw) is enabled
error |11:48:04: [openLoadFile] file components/weapons/cy_miss2.pie
could not be opened: The system cannot find the file specified.
error |11:48:04: [openLoadFile] Assert in Warzone:
..\lib\framework\frame.c:309 (!unable to open file), last script event:
'none'
error |11:48:26: [resLoadFile] resLoadFile: Unable to retreive resource
- components/weapons/cy_miss2.pie
fatal |11:48:26: [resLoad] Failed to parse wrf/piestats.wrf
info|11:48:29: [startMultiplayerGame] Unable to load piestats.
Defaults not set.
error |11:48:29: [res_error] RES file parse error:
syntax error at line 238
Text: '/***/
'
fatal |11:48:29: [resLoad] Failed to parse wrf/vidmem.wrf
fatal |11:48:31: [startGameLoop] Shutting down after failure
}}}
--
Ticket URL: http://developer.wz2100.net/ticket/1748
Warzone 2100 Trac http://developer.wz2100.net/
The Warzone 2100 Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1749: dydo-ai bug
#1749: dydo-ai bug
-+--
Reporter: Crymson |Type: bug
Status: new |Priority: major
Milestone: unspecified | Component: other
Version: svn/trunk |Keywords:
Operating_system: All/Non-Specific | Blockedby:
Blocking:|
-+--
{{{
info|11:43:57: [SDL_main] mod_mp (dydo-ai) is enabled
error |11:44:38: [strresGetString] Could not find string for id
A0HardcreteMk1Gate
error |11:44:38: [strresGetString] Assert in Warzone:
..\lib\framework\strres.c:100 (string), last script event:
'none'
fatal |11:45:06: [allocateName] Unable to find string resource for
A0HardcreteMk1Gate
}}}
The logo on the main screen is too tall!
--
Ticket URL: http://developer.wz2100.net/ticket/1749
Warzone 2100 Trac http://developer.wz2100.net/
The Warzone 2100 Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Ticket #1746
http://developer.wz2100.net/ticket/1746 It seemed easier to continue this discussion via the ML rather than in the comments of the ticket. = Changed 10 hours ago by Zarel Replying to stiv: We don't want to have any more betas. The fact that we are approaching 15 is simply appalling and a sign of a software development process that is out of control. NO MORE NEW FEATURES DURING THE BETA! Well, then, perhaps you guys should fix your development process, then, but I don't see what that has to do with my patch. That is exactly what we are trying to do - fix *our* development process. The reason your patch comes into it is because it adds an untested feature to an extremely brittle code base in the midst of a beta period that has gone on far, far too long. We need to stop doing this if we want to have a 2.3 release. This is why fixing the mod system is a target for 2.3.1. New features go into trunk. If we can actually get a release of 2.3 out the door, 2.3.1 can follow soon after. So you propose releasing a feature with practically no testing (I presume that's what you mean by soon after), instead of the testing I my proposal would do? You are putting words in my mouth. I can always tell when you feel your case is lost because you start creating strawmen and spurious objections. One of the principles of Open Source software development is Release early, release often. The way we do that is by controlling what goes into each release. That is what I mean by 'soon after'. -- Stephen Swaney sswa...@centurytel.net ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
