public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Hans Ronne <hronne@telia.com>
To: Jim Kingdon <kingdon@panix.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Downloading Xconq
Date: Thu, 12 Jun 2003 17:54:00 -0000	[thread overview]
Message-ID: <l03130300bb0d0ce5bf10@[212.181.162.155]> (raw)
In-Reply-To: <200306111553.h5BFrcJ24864@panix5.panix.com>

>> I've been holding off on full distributions since I didn't want an
>> incomplete and buggy version to be widely distributed.
>
>Well, I'd go more with "release early and often" (
>http://www.openresources.com/documents/cathedral-bazaar/node4.html ),
>especially now that the bugs in the networking code are fixed.

I've been planning to put snapshots on the sourceware ftp site, like Stan
used to do before a new release. That would help the final debugging and
perhaps trigger a little more user feedback than I usually get.

I'm rather optimistic about the time schedule since xconq itself is in a
good shape now. I have also completed the bug fixes and improvements to
imfapp. I've now started to look over the game modules, which has not been
done for ages.

Hans


  reply	other threads:[~2003-06-11 17:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 17:32 Bill Macon
2003-06-11  3:17 ` Hans Ronne
2003-06-11 17:44   ` Jim Kingdon
2003-06-12 17:54     ` Hans Ronne [this message]
2003-06-11 15:53 ` Elijah Meeks
2003-06-29 15:03   ` Erik Jessen
2003-06-29 15:03     ` Hans Ronne
2003-06-29 15:06     ` Eric McDonald
2003-06-29 15:06       ` Hans Ronne
2003-06-29 16:55         ` Eric McDonald
2003-06-30  5:16           ` Hans Ronne
2003-06-29 15:17     ` Elijah Meeks
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 14:13 Advanced Unit Damage Hans Ronne
2003-06-10 17:08 ` Downloading Xconq Elijah Meeks

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='l03130300bb0d0ce5bf10@[212.181.162.155]' \
    --to=hronne@telia.com \
    --cc=kingdon@panix.com \
    --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).