Re: Prepare and prepare ?

Поиск
Список
Период
Сортировка
От Rudy Lippan
Тема Re: Prepare and prepare ?
Дата
Msg-id Pine.LNX.4.44.0303262314140.8903-100000@elfride.ineffable.net
обсуждение исходный текст
Ответ на Re: Prepare and prepare ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: Prepare and prepare ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Prepare and prepare ?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-interfaces
On Wed, 26 Mar 2003, Bruce Momjian wrote:

> OK, so you are saying that the code as exists now in CVS is ready for
> release, and once we release, you want to add a lot of stuff, right? 
> And there is nothing that needs work _before_ we do a release?

Bruce, 

1.21 + UTF-8 patch should be ready to be released as 1.22. We can skip
putting up a 1.22 and jump right to 1.30 alpha if we don't see a need for
getting out the UTF patch?  I am easy on this point. So do we want a 1.22
or do we want to jump right to a 1.30 alpha?


The 'a lot of stuff' is already in CVS on the 1_30 branch.  I put it there
because I thought we were going to be releasing a 1.22 for basic UTF
support, but since then CVS head has gathered a few other patches that are
not ready for release :(

What I am planing on doing is copying 1_30 over cvs head, making an alpha
release based on that, and then merging all of the patches that were added
since 1.21. (And all new patches against CVS head will be easier to 
apply).


The patch that is on the 1_30 branch is here:  
ftp://gborg.postgresql.org/pub/dbdpg/1/dbd_pg.patch and I think it would
be much easier to merge a few minor patches rather than the other way
around :)

Thoughs?


Rudy



В списке pgsql-interfaces по дате отправления:

Предыдущее
От: Stephan Szabo
Дата:
Сообщение: Re: [GENERAL] Persistent variables between cross-calls in C functions
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Prepare and prepare ?