public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Jim Kingdon <kingdon@panix.com>
To: mcdonald@phy.cmich.edu
Cc: xconq7@sources.redhat.com
Subject: Re: Changing the Standard Game
Date: Sun, 05 Sep 2004 20:09:00 -0000	[thread overview]
Message-ID: <200409051958.i85JwQ805142@panix5.panix.com> (raw)
In-Reply-To: <413B3DFC.7020208@phy.cmich.edu> (message from Eric McDonald on Sun, 05 Sep 2004 10:25:32 -0600)

> I still have no idea when the 7.5 release is going to be. Up until
> recently, I have restrained myself from taking on any big projects
> (such as UI building) because I didn't want to have 7.5 announced
> while I was in the middle of one, and I certainly did not want to hold
> up a release on account of my work.

Experience in other projects seems to be that the whole business of
branching/freezing/etc doesn't work particularly well, and you are
better off making sure that the mainline is always in good shape.

For example, see http://lwn.net/Articles/95312/

Now, we could use better ways of keeping the mainline sane than we
have now.  My pet solution is automated tests, but since I'm not
writing much xconq code (or tests) these days, that doesn't count for
as much as what the more active developers do.  Another way is to
publish and encourage public testing of big, or risky, changes before
checking them in.  We're low on testers in general, which is the big
risk factor with that one.

As for wanting to keep working on SDL, if you are talking about code
which is specific to SDL, I can't think of any reason to be at all
reluctant to touch it on account of a supposedly-imminent 7.5 release.
If it is non-SDL code, well, maybe then there's more of an issue.  But
the idea of stabilizing the SDL code by not hacking on it doesn't
really make sense, given how much is missing in the current SDL code.

> I am aware that there are some network bugs out there that need to
> be fixed.

Yeah, and I wonder if there is a better way to find these than "find
another human who wants to play a network game and get a few turns in
and get a loss of sync".  AI vs AI network games are the traditional
method, and perhaps the current problem is just that no one has tried
one lately.  Writing some kind of monkey tester might be another way
(which generates random events, hopefully hitting corner cases which
the AI happens not to hit).  Finding a way to run these tests
(whatever they are) more quickly/automatically would be a big step up.

  reply	other threads:[~2004-09-05 19:58 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040827050942.5961.qmail@web13122.mail.yahoo.com>
2004-08-27 17:09 ` CXP??? Eric McDonald
2004-08-28  2:51   ` CXP??? Elijah Meeks
2004-08-28  3:47     ` Multiple Image Use Elijah Meeks
2004-08-28  4:02       ` Eric McDonald
2004-08-28  4:33         ` Elijah Meeks
2004-09-01  7:30         ` Standard Game Graphics Elijah Meeks
2004-09-01 16:18           ` Jim Kingdon
2004-09-01 18:30             ` Eric McDonald
2004-09-02  1:43               ` Elijah Meeks
2004-09-02  4:24                 ` Eric McDonald
2004-09-03  2:30                 ` Jim Kingdon
2004-09-03  3:01                   ` Elijah Meeks
2004-09-03  3:17                     ` Eric McDonald
2004-09-03  5:10                       ` Elijah Meeks
2004-09-03  5:11                         ` Jim Kingdon
2004-09-03  6:10                         ` Jim Kingdon
2004-09-03 17:18                           ` Changing the Standard Game Elijah Meeks
2004-09-04  2:06                             ` Eric McDonald
2004-09-04 17:46                             ` Lincoln Peters
2004-09-05  1:48                               ` Eric McDonald
2004-09-05  6:02                                 ` Feature Request: Advance Prohibits Advance Elijah Meeks
2004-09-05 16:25                                   ` Eric McDonald
2004-09-05 16:41                                     ` mskala
2004-09-05 16:54                                       ` Eric McDonald
2004-09-05 17:11                                         ` mskala
2004-09-05 17:01                                       ` Elijah Meeks
2004-09-05 16:48                                     ` Elijah Meeks
2004-09-05 19:43                                       ` Eric McDonald
2004-09-05 16:50                                     ` mskala
2004-09-05 16:55                                       ` Eric McDonald
2004-09-05 16:55                                   ` Lincoln Peters
2004-09-05 17:01                                     ` Elijah Meeks
2004-09-05 19:52                                       ` Jim Kingdon
2004-09-05 20:16                                         ` Eric McDonald
2004-09-05 19:58                                       ` Lincoln Peters
2004-09-05 20:15                                         ` Elijah Meeks
2004-09-05 15:52                                 ` Changing the Standard Game Lincoln Peters
2004-09-05 16:36                                   ` Eric McDonald
2004-09-05 20:09                                     ` Jim Kingdon [this message]
2004-09-05 20:14                                 ` Jim Kingdon
2004-09-05 20:40                                   ` Elijah Meeks
2004-09-05 22:09                                   ` Eric McDonald
2004-09-03 23:11                         ` Standard Game Graphics Eric McDonald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200409051958.i85JwQ805142@panix5.panix.com \
    --to=kingdon@panix.com \
    --cc=mcdonald@phy.cmich.edu \
    --cc=xconq7@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).