public inbox for
 help / color / mirror / Atom feed
From: 'Chad Walstrom' <>
To: David S Gathright <>
Subject: Re: 4.1.0 Release Candidate: gnats-4_1_0-rc2
Date: Mon, 28 Feb 2005 17:40:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1273 bytes --]

David S Gathright wrote:
> What's the timeframe looking like for the 4.1 release?  We're about to
> move into a (much) larger scale deployment of the GNATS system and I'd
> prefer not to upgrade the GNATS system just after that.

I'm CC'ing to soliciting opinions.  I wanted to make
sure we could build on all platforms before releasing.  I believe there
were a couple FreeBSD issues with rc1 [1]_ that I hope have gone away
now that we've dropped libiberty and friends.

We need some testing, essentially.  Once we confirm that everything
compiles on platforms that GNATS is used, I'll tag the release in CVS
and roll the tarball.

One thing that I've run in to is making sure that getdate.c doesn't get
recompiled using bison > 1.35.  Bison 1.875d, the default on Debian,
does not produce viable output with our getdate.y file. This might be a
good candidate for gnulib addition.  I'll send a bug to bug-gnats.  In
any case, if you don't rebuild getdate.c or if you use bison 1.35,
everything seems to compile just fine.

.. [1]

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  parent reply	other threads:[~2005-02-28 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26  1:38 Chad Walstrom
     [not found] ` <>
2005-02-28 17:40   ` 'Chad Walstrom' [this message]
2005-03-03 17:34     ` 'Chad Walstrom'

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:

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

  git send-email \ \ \ \ \

* 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).