forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian G. Haas" <>
Subject FOR-430 and FOR-433 [was Re: planning for 0.7 release]
Date Wed, 23 Feb 2005 18:52:27 GMT

considering prerelease time is usually bugfix time, are any committers
currently reviewing FOR-430 and FOR-430? I submitted patches for these
a few weeks ago (like I suppose other contributors have for issues
reported by them, too).

Not trying to sound like the impatient type -- which I nonetheless am,
as I'll readily admit :-) -- but it seems to me that a few past
patches by contributors haven't made it into the trunk simply for
having gone unnoticed, rather than being rejected by committers.

I hope I've worded this diplomatically enough, as I definitely don't
want to downplay the achievements of the Forrest project team,
criticize any committer's behavior, or question anyone's judgment. You
guys are doing an awesome job.

Best regs,

On Wed, Feb 23, 2005 at 06:49:18PM +1100, David Crossley wrote:
> Ross Gardler wrote:
> > David Crossley wrote:
> > >It takes quite a while to get ready for a release. It would be good
> > >to wait until Ross can help a bit because plugins is the major change
> > >for this release. I will also be busy for the next two weeks.
> > 
> > Is there something specific you have in mind, or do you just want me on 
> > hand if problems arise?
> The latter. Actually it is good to have as many committers as possible
> available during the lead up to release. It was a lot of work to get the
> 0.6 release out. I expect that 0.7 will be easier, as we solved a lot of
> issues last time.
> > (Getting the documentation published, even if only in a manual way would 
> > be important for example).
> Do you mean the documentation for the various plugins?
> > >Should we aim for a release date of Friday 2005-03-25?
> > 
> > SInce it's Nicola's birthday I think that is a must - two excuses for a 
> > beer in the evening.
> That is a date then.
> --David

Florian G. Haas <>

GnuPG key ID: 0x46D00BE3
Key fingerprint: 18B4 3E7B 191E F534 254A  1F7C 816D 950B 46D0 0BE3

My GnuPG key is available from the public PGP key server at (and various other key servers).

View raw message