Ühel kenal päeval, T, 2007-10-09 kell 22:36, kirjutas Stefan
> Bruce Momjian wrote:
> > Andrew Dunstan wrote:
> >>
> >> Bruce Momjian wrote:
> >>> Tom Lane wrote:
> >>>   
> >>>> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >>>>     
> >>>>> I don't see how timing has anything to do with this.  You could have
> >>>>> added it between beta1 and beta2 after sufficient hackers discussion. 
> >>>>>       
> >>>> Uh, it *was* after beta1.
> >>>>     
> >>> Oh, so it didn't hold up beta1 --- that's good.
> >>>
> >>>   
> >> No it's not.
> >>
> >> Can somebody please explain to me what beta means if you can commit new 
> >> stuff after it has been declared?
> > 
> > We allow /contrib to be more lax about beta changes.
> the postgresql ecosystem is growing and there is a lot of people like
> packagers that will be a quite irritated if we keep randomly adding
> completely new code and modules during BETA.

Should packagers be concerned with /contrib at all ?

As noted before /contrib is a technical way of ensuring that something
gets updated together with core, not a recommendation to include it in a

Arguably, a good packager should make its own decisions about what to
include in his/her/its packages, which may include stuff from pgfoundry
and also may omit stuff from /contrib .


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to