Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10607] branches/2.3/data/mods/multiplay/dydo-ai
On Sat, Apr 17, 2010 at 3:11 PM, dydo...@users.sourceforge.net wrote: maps for dydo challenges Added Paths: --- branches/2.3/data/mods/multiplay/dydo-ai/maps/ branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-AllEqual.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-Arena_14.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/CNCAssualt.wz Who made these maps? - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10607] branches/2.3/data/mods/multiplay/dydo-ai
On Saturday, 17 April 2010 at 15:31, Per Inge Mathisen wrote: On Sat, Apr 17, 2010 at 3:11 PM, dydo...@users.sourceforge.net wrote: maps for dydo challenges Added Paths: --- branches/2.3/data/mods/multiplay/dydo-ai/maps/ branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-AllEqual.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-Arena_14.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/CNCAssualt.wz Who made these maps? And for some more questions: Why are they in .wz format? If they're included in the game, people will have them anyway, so they can be uncompressed. Also, why not put them in the main data, so they can be used for all types of games (that goes for the maps in ntw as well)? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[10607] branches/2.3/data/mods/multiplay/dydo-ai
On Saturday, 17 April 2010 at 15:31, Per Inge Mathisen wrote: On Sat, Apr 17, 2010 at 3:11 PM, dydo...@users.sourceforge.net wrote: maps for dydo challenges branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-AllEqual.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/4c-Arena_14.wz branches/2.3/data/mods/multiplay/dydo-ai/maps/CNCAssualt.wz Who made these maps? AllEqual seems to be a converted map for the original game, couldn't find out who made it. Arena #14 is by Olrox, http://forums.wz2100.net/viewtopic.php?f=10t=4875 CNCAssualt by DraLUSAD, http://forums.wz2100.net/viewtopic.php?f=10t=4799 ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] [Warzone 2100 Trac] #1782: Add shadows for susbtitles
#1782: Add shadows for susbtitles -+-- Reporter: Emdek |Type: patch Status: new |Priority: trivial Milestone: 2.3 | Component: Engine: Graphics Version: svn/trunk |Keywords: Operating_system: All/Non-Specific | Blockedby: Blocking:| -+-- This patch adds shadows for subtitles to make them more readable on bright backgrounds -- Ticket URL: http://developer.wz2100.net/ticket/1782 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] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. If the Dydo changes can't be rectified, then we will do what we did the the 2.3_rc1a tag. The 2.3.0 release should be done on 4/24/10. Are we all in agreement? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On Saturday, 17 April 2010 at 15:45, buginator wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Actually, I'd branch 2.3.0 from the rc tag as soon as possible, since the whole point of branching is that the 2.3 branch then is not frozen, only the 2.3.0 branch (which then can get selected backports from 2.3). Zarel proposed a tag instead of a branch for 2.3.0, to which we commit until the final release. Doesn't matter much to me, it's all the same anyway in svn. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Getting the word out about 2.3.0 ?
Once 2.3.0 has been released, we need to get the word out to all the sites that we hit before, and all the others that link to the 2.2.x series. For now, all old links have been broken, except for these: http://download.gna.org/warzone/releases/ http://download.gna.org/warzone/snapshots/ Whoever has access to gna, if they can move http://download.gna.org/warzone/releases/ to http://download.gna.org/warzone/archive/releases/ and http://download.gna.org/warzone/snapshots/ to http://download.gna.org/warzone/archive/snapshots/ it would be appreciated. For the release announcements, I am not a very good wordsmith, so if someone can write something for 2.3.0. that would be great. The announcement will be used in our front page, and on all the sites where we want to send announcements to. So far, the list is: http://linuxgames.com/ http://happypenguin.org/ http://linux-gamers.net/ http://freshmeat.net/projects/warzone2100/ http://warzone-2100.en.softonic.com/ windows specific: http://www.moddb.com/games/275/warzone-2100 http://www.gamershell.com/news/ http://www.gamedev.net/community/forums/forum.asp?forum_id=6 (?? who has account here?) Apple specific: (need user account) http://www.apple.com/downloads/macosx/games/role_strategy/warzone2100.html Did I miss any? Volunteers are also needed for this huge task. The changelog also needs to be fixed(?). The stuff in doc/*.* what shall we do with this stuff? Anything else? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On Sat, Apr 17, 2010 at 2:45 PM, buginator buginato...@gmail.com wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Yeah, that was my idea. If it's frozen, we might as well tag 2.3.0. Leaves 2.3-branch open for 2.3.1 commits. The 2.3.0 release should be done on 4/24/10. Man, I'm gonna have to rush the new layout. :( -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Getting the word out about 2.3.0 ?
On Sat, Apr 17, 2010 at 7:24 PM, buginator buginato...@gmail.com wrote: So far, the list is: ... Did I miss any? Yeah; let's announce to Slashdot. ;) Anything else? We should have a summary changelog with a list of what's new; preferably with corresponding pictures. -Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Getting the word out about 2.3.0 ?
On Saturday, 17 April 2010 at 20:24, buginator wrote: So far, the list is: http://linuxgames.com/ http://happypenguin.org/ http://linux-gamers.net/ http://freshmeat.net/projects/warzone2100/ We could also announce the RC on those sites, to get it a bit more exposed (though we'd need at least a rough changelog since 2.2 for that). ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] 2.3 code freeze until 2.3.0 branch, 2.3.0 release target date 4/24/10
On 4/17/10, Christian Ohm wrote: On Saturday, 17 April 2010 at 15:45, buginator wrote: Let's try this again, 2.3 is in a code freeze, and ONLY show stopping bugs will be fixed. It was suggested that we branch 2.3.0 from svn head, once we know the status of the Dydo changes. Actually, I'd branch 2.3.0 from the rc tag as soon as possible, since the whole point of branching is that the 2.3 branch then is not frozen, only the 2.3.0 branch (which then can get selected backports from 2.3). Zarel proposed a tag instead of a branch for 2.3.0, to which we commit until the final release. Doesn't matter much to me, it's all the same anyway in svn. Ok, I am fine with either a tag or a branch, as soon as Per OKs it, then whoever can tag it. He might want to get his .02 on this issue, and if we don't hear from Per by Sunday evening, then we can just make the branch or tag then. I only know of 2 patches that need to be applied so far... ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
