wesnoth-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Wesnoth-dev] Next release?


From: Guillaume Melquiond
Subject: Re: [Wesnoth-dev] Next release?
Date: Sun, 14 Nov 2004 08:52:19 +0100

On Sat, 13 Nov 2004 20:04:39 -0600, David White
<address@hidden> wrote:
> There's at least one reasonably serious bug I know of: if you go onto
> the server, and load a multiplayer game, many of the widgets don't display.

Indeed, I just reproduced it.

> I suspect (?) this is caused by silene's changes to some widgets.
> Silene: can you investigate?

No, I don't think it is caused by my changes. There have been two kind
of widgets changes recently, my rewrite of the low-level widgets, and
Ayin's write of a high-level widget to display a scrolling lobby (a
really good-looking feature). Both are linked, since my rewrite made
Ayin's write a lot easier.

Anyway, I know this part of the code, so I can investigate it (and
it's probably quite simple, a few "hide" methods not called when
loading multiplayer, I suspect). But unfortunately, I will be away
from wesnoth development till Monday the 22th (I shouldn't even be
answering this mail, I should be packing my luggages...). So, unless
Ayin is also away, he will probably be the one to take a stab at it.

> There is also a known out-of-sync bug, which has to be fixed at some
> stage...

Right, this one is kind of showstopper for 1.0. How are the OoS stats
of wesnothd looking at the moment? (wasn't there a way to query the
server, or am I just imagining things?)

> Other than that, I think we are ready for a new release soon.
> 
> I am still of the opinion that we should consider branching soonish. My
> main concern with that is that the Heir to the Throne campaign is still
> unbalanced/poor quality in the later scenarios, and I think it should be
> fixed up before a branch.
> 
> If we branched, I think that I should be the maintainer of one branch,
> and Ayin or silene should be the maintainer of the other.
> 
> The alternative approach, of course, would just be to cool off on
> features until we can release 1.0.

I think it is important we start working with two branches, a bug-fix
branch and a development branch. And after 1.0 release, maybe three
branches: the stable 1.0 branch, the nice looking branch 1.4.25, the
development branch 1.5 (which will lead to the next 1.6 nice looking
branch). I don't mind managing a branch.

> I guess the big question wrt 1.0 is what is not in the game currently
> that people want in there? Once again, my biggest concern is that the
> Heir to the Throne campaign isn't polished enough at the moment. In
> terms of features, I think we are good enough now for 1.0, although some
> more polishing doesn't hurt.
> 
> David

I don't know how advanced Ayin's lobby rewrite (not just the widget as
already present in CVS, but the underlying architecture) is. But I
would like to see it finished. Indeed I hope it will solve all the
synchronization/refresh problems at multiplayer game creation time.
This polish is a must have for 1.0 imho.

Guillaume




reply via email to

[Prev in Thread] Current Thread [Next in Thread]