[warzone2100-dev] [Warzone 2100 Trac] #1762: DyDo Challenge

[Warzone 2100 Trac]

#1762: DyDo Challenge
--+-
Reporter:  w...@…  |Type:  bug   
  Status:  new|Priority:  major 
   Milestone:  2.3.1  |   Component:  Data: Maps
 Version:  2.3 beta 12a (svn r10492)  |Keywords:
Operating_system:  GNU/Linux  |   Blockedby:
Blocking: |  
--+-
 missing maps Sk-Arctic-T1 and Sk-CNCAssualt-T1 in beta13

 info|04:49:05: [main] mod_mp (dydo-ai.wz) is enabled
 error   |04:49:55: [loadMapPreview] Could not find level dataset!
 error   |04:49:55: [loadMapPreview] Assert in Warzone: multiint.c:281
 (psLevel), last script event: ''
 error   |04:50:02: [loadMapPreview] Could not find level dataset!
 error   |04:50:02: [loadMapPreview] Assert in Warzone: multiint.c:281
 (psLevel), last script event: ''
 error   |04:50:19: [openLoadFile] file Sk-Arctic-T1 could not be opened:
 File not found
 error   |04:50:19: [openLoadFile] Assert in Warzone: frame.c:306 (!"unable
 to open file"), last script event: ''
 fatal   |04:50:19: [resLoad] Could not open file Sk-Arctic-T1
 fatal   |04:50:19: [startGameLoop] Shutting down after failure

 info|05:01:34: [main] mod_mp (dydo-ai.wz) is enabled
 error   |05:01:44: [openLoadFile] file Sk-CNCAssualt-T1 could not be
 opened: File not found
 error   |05:01:44: [openLoadFile] Assert in Warzone: frame.c:306 (!"unable
 to open file"), last script event: ''
 fatal   |05:01:44: [resLoad] Could not open file Sk-CNCAssualt-T1
 fatal   |05:01:44: [startGameLoop] Shutting down after failure

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[warzone2100-dev] Project status after 2.3 release

[buginator]

It is getting very close to the release of 2.3, so I figure we should
sort a few things out before we hit the launch button.

Trac tickets basically boil down into tickets that are:
a) useless.  (can't replicate, no good info in said ticket)
b) general corruption.  (can't replicate)
c) other corruption (can't replicate)
d) we know about it, but no fix yet.

It really doesn't do us any good to keep a,b & c tickets open.
I recommend we set all those to pending information (ie, a way to replicate).

On the release of 2.3, I recommend we have a transition period for the
lobby server that will tell 2.2.x clients to upgrade to 2.3 ASAP, then
after 2-3 weeks or so, we just echo the message of 'Update to 2.3' and
close the connection.
This will help our online community get much bigger, and not splinter
them with different versions floating around.

On Qt, everyone should basically try and help out to get this branch
working correctly on all platforms, in preparation for the merge to
trunk.

At that point, I feel a branch to 2.5 (or whatever is in order) to get
testing done ASAP.

Once this has completed, then we can work on newnet, and fix the
issues it has on windows machines, and of course, we also have the lua
branch which is roughly 55-65% completed.

If at all possible, we should try to not have any new features in the
beta releases, and leave them as bug fixes only, and do a 'release
early, release often' policy.

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

[warzone2100-dev] [Warzone 2100 Trac] #1763: QWZM todo, tofix, etc.

[Warzone 2100 Trac]

#1763: QWZM todo, tofix, etc.
---+
 Reporter:  Safety0ff  |  Owner:  Safety0ff   
 Type:  to-do  | Status:  new 
 Priority:  trivial|  Milestone:  unspecified 
Component:  other  |Version:  unspecified 
 Keywords: |   Operating_system:  All/Non-Specific
Blockedby: |   Blocking:  
---+
 This ticket is to keep track of what I have left to do and so people can
 add bugs that I might have missed.

 Off the top of my head:

 What I've done so far:[[BR]]
 -PIE export(85% done)[[BR]]
 -Merged PIE and WZM opening into one dialog[[BR]]
 -Ability to display single mesh[[BR]]
 -Turned on blending (improves transparency in textures)[[BR]]
 -Improved handling of the case where textures aren't found in hardcoded
 path[[BR]]

 Planned:[[BR]]
 -Fix/complete add/remove connector/frame.[[BR]]
 -ANI saving/loading.

 Issues to fix:
 - Berg mentioned pie flag issues.

-- 
Ticket URL: 
Warzone 2100 Trac 
The Warzone 2100 Project
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev

Re: [warzone2100-dev] Project status after 2.3 release

[Guangcong Luo]

On Sun, Apr 11, 2010 at 1:36 PM, buginator  wrote:
> On the release of 2.3, I recommend we have a transition period for the
> lobby server that will tell 2.2.x clients to upgrade to 2.3 ASAP, then
> after 2-3 weeks or so, we just echo the message of 'Update to 2.3' and
> close the connection.
> This will help our online community get much bigger, and not splinter
> them with different versions floating around.

I think we should wait twice as long, but otherwise I agree. As far as
I know, most of our users are on 2.3, anyway, and forcing the rest to
upgrade will just piss off the rest who won't/can't upgrade.

Anyway, w.r.t. to our future, I have a new idea: We branch 2.4 right
before merging in Qt and newnet. Trunk is reasonably stable, and the
last time we branched trunk was over a year ago. Getting current trunk
to stable should be a reasonably fast process, but debugging Qt and
newnet could be very long-term stuff.

-Zarel

___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev