> > Well, a third party author always has the option to release his code
> > separately on whatever timeline seems good to him. But I think that for
> > third-party code included in the distribution, the same standards ought
> > to apply as for the Postgres code itself: we don't want people stick
The Hermit Hacker <[EMAIL PROTECTED]> writes:
> On Thu, 5 Oct 2000, Tom Lane wrote:
>> [EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
When is 7.1 being locked down? I may be releasing 3.1 with a few small
fixes and changes very soon.
>>
>> You've probably got about 2 weeks before beta st
November 1.
> Thus spake Bruce Momjian
> > I have installed this in the current source tree, ready for 7.1.
> >
> > I have installed >
> > > Announce: Release of PyGreSQL version 3.0
>
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> fixes and changes very soon.
>
>
[EMAIL PROTECTED] (D'Arcy J.M. Cain) writes:
> When is 7.1 being locked down? I may be releasing 3.1 with a few small
> fixes and changes very soon.
You've probably got about 2 weeks before beta starts. Bug fixes are
accepted during beta freeze, of course --- just no new-feature
development.
