On 8/24/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
>
> It has been done... Now let's pray. ;)
>
> Charlie Goodwin has been nice enough to dedicate today's post on his
> popular blog to this release ( http://freegamer.blogspot.com/ ) so I
> think we have a little bit of momentum right now. Bina
On 8/23/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> On 8/22/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> > On 8/22/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> > >
> > > I have an evening free now, so I can create the release within the
> > > next six hours or so. Just give a green
On 8/22/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> On 8/22/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> >
> > I have an evening free now, so I can create the release within the
> > next six hours or so. Just give a green light and I'll do it.
> >
> > ~Daniel
> >
>
> Got preoccupied wit
On 8/22/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
>
> I have an evening free now, so I can create the release within the
> next six hours or so. Just give a green light and I'll do it.
>
> ~Daniel
>
Got preoccupied with RL matters so I won't have time tonight after
all. Will try again in 24
On 8/22/07, Christian Knoke <[EMAIL PROTECTED]> wrote:
> Daniel Markstedt wrote on Aug 22, 07:35 (+0900):
>
> > Very well, I'll go ahead and do the release today then! In, say, seven
> > hours or so.
>
> I'd suggest to have a grace period between the time you're (thinking
> you're) ready for beta r
Daniel Markstedt wrote on Aug 22, 07:35 (+0900):
> Very well, I'll go ahead and do the release today then! In, say, seven
> hours or so.
I'd suggest to have a grace period between the time you're (thinking
you're) ready for beta release, and the actual release, of 1 to 3 days,
to give people with
Any ideas regarding PR#39589 (Windows gettext problems)?
The submitted gettext.m4 patch still doesn't completely solve the
detection problem, since it might now be possible (but on Windows
only) that gettext gets falsely "detected" in libintl even if the
libintl.a file is actually missing (but lib
On 22/08/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
>
> The only thing I see is the PR#39599 and PR#39600, as they are needed to
> compile
Tested that #39600 would not break compilation here. All clients
(gtk/sdl/xaw/ftwl/stub) compile with (or without) it.
...sdl client froze whe
Marko Lindqvist wrote:
> But we agree that earlier release would be better than waiting for
> this? I can accept waiting up to Sunday, though.
>
Oh, absolutely!
The only thing I see is the PR#39599 and PR#39600, as they are needed to
compile
___
F
On 22/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> On 8/22/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote:
> > On 21/08/07, William Allen Simpson <[EMAIL PROTECTED]>
> >
> > > Friday?!?! I thought we were going to do it yesterday
> >
> > Daniel? If you reschedule, just let us know in a
On 8/22/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote:
> On 21/08/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
> > Daniel Markstedt wrote:
> > > Fine, I'll schedule a new release for Friday then. Would that give you
> > > enough time to root out any obvious issues?
>
> I don't expect many
On 21/08/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
> Daniel Markstedt wrote:
> > Fine, I'll schedule a new release for Friday then. Would that give you
> > enough time to root out any obvious issues?
I don't expect many issues as we have already been preparing for
release since last we
Daniel Markstedt wrote:
> Fine, I'll schedule a new release for Friday then. Would that give you
> enough time to root out any obvious issues?
>
Friday?!?! I thought we were going to do it yesterday
I'll see whether I can re-architect Pepeto's goto fixes. Cannot promise
anything. But I was
On 8/21/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote:
> On 21/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> > On 8/21/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
> > > (PR#39596) 2.1.0 capability cleanup
> > >
> >
> > Good. So what's left to do before release? Your po cleanup, Mark
On 21/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> On 8/21/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
> > (PR#39596) 2.1.0 capability cleanup
> >
>
> Good. So what's left to do before release? Your po cleanup, Marko?
No, po thing cannot continue before release.
Otherwise we ne
On 8/21/07, William Allen Simpson <[EMAIL PROTECTED]> wrote:
> (PR#39596) 2.1.0 capability cleanup
>
Good. So what's left to do before release? Your po cleanup, Marko?
~Daniel
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listi
(PR#39596) 2.1.0 capability cleanup
___
Freeciv-dev mailing list
Freeciv-dev@gna.org
https://mail.gna.org/listinfo/freeciv-dev
On 20/08/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote:
> On 20/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> >
> > Is there a ticket for the network compatibility issue in the tracker,
> > so I can know when it has been resolved?
>
> I'll create one tonight.
Probably not. RL reasons.
On 20/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
>
> Is there a ticket for the network compatibility issue in the tracker,
> so I can know when it has been resolved?
I'll create one tonight.
Then we have to see that at least some of the most basic tests are
done. Such as seeing that all
On 8/19/07, Marko Lindqvist <[EMAIL PROTECTED]> wrote:
> On 19/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> > Less than 24h remain until the time when I intended to create the
> > 2.1.0-beta6 release. However, Marko has asked me to postpone it to
> > sort out a network protocol incompatibil
On 19/08/07, Daniel Markstedt <[EMAIL PROTECTED]> wrote:
> Less than 24h remain until the time when I intended to create the
> 2.1.0-beta6 release. However, Marko has asked me to postpone it to
> sort out a network protocol incompatibility issue, so I won't force
> that deadline.
>
> What other cri
Daniel Markstedt wrote:
> Less than 24h remain until the time when I intended to create the
> 2.1.0-beta6 release. However, Marko has asked me to postpone it to
> sort out a network protocol incompatibility issue, so I won't force
> that deadline.
>
> What other critical issues remain to get this
Less than 24h remain until the time when I intended to create the
2.1.0-beta6 release. However, Marko has asked me to postpone it to
sort out a network protocol incompatibility issue, so I won't force
that deadline.
What other critical issues remain to get this out the door?
Remember this is not
23 matches
Mail list logo
