Thread: Vote Release number of the next.
Hi. I think the vote of the next release number. 1.) 09.01.0300 many patch is a bug-fix support. and, psqlODBC is not intended to be synchronized with postgres version number. 2.) 09.02.0100 new version is desirable because test code that contains. 3.) 09.03.0100 we want to have a postgres release the next number. == I vote to 1.) , I think the major version up, when there is a change of more features and desirable. thanks! Regards, Hiroshi Saito
I also vote for 09.01.0300. I thought since we were compiling with 9.1 PostgreSQL headers that is where the "09.01" came from, or is that just a happy coincidence? Thanks...jack -- View this message in context: http://postgresql.1045698.n5.nabble.com/Vote-Release-number-of-the-next-tp5755600p5755696.html Sent from the PostgreSQL - odbc mailing list archive at Nabble.com.
On Wed, May 15, 2013 at 3:51 PM, Hiroshi Saito <hiroshi@winpg.jp> wrote: > Hi. > > I think the vote of the next release number. > > 1.) 09.01.0300 > many patch is a bug-fix support. and, psqlODBC is not intended > to be synchronized with postgres version number. Yes it is - we used to have some users get confused about what they should use, so we decided to link the version number to the current database server version number. There is no technical reason for linking them. > 2.) 09.02.0100 > new version is desirable because test code that contains. > > 3.) 09.03.0100 > we want to have a postgres release the next number. > > == > I vote to 1.) , I think the major version up, when there is a > change of more features and desirable. > thanks! > > Regards, > Hiroshi Saito > > > -- > Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-odbc -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Which, btw, means it should really be 09.02.0100, unless we're going to change the scheme. On Thu, May 16, 2013 at 8:22 AM, Dave Page <dpage@pgadmin.org> wrote: > On Wed, May 15, 2013 at 3:51 PM, Hiroshi Saito <hiroshi@winpg.jp> wrote: >> Hi. >> >> I think the vote of the next release number. >> >> 1.) 09.01.0300 >> many patch is a bug-fix support. and, psqlODBC is not intended >> to be synchronized with postgres version number. > > Yes it is - we used to have some users get confused about what they > should use, so we decided to link the version number to the current > database server version number. There is no technical reason for > linking them. > >> 2.) 09.02.0100 >> new version is desirable because test code that contains. >> >> 3.) 09.03.0100 >> we want to have a postgres release the next number. >> >> == >> I vote to 1.) , I think the major version up, when there is a >> change of more features and desirable. >> thanks! >> >> Regards, >> Hiroshi Saito >> >> >> -- >> Sent via pgsql-odbc mailing list (pgsql-odbc@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-odbc > > > > -- > Dave Page > Blog: http://pgsnake.blogspot.com > Twitter: @pgsnake > > EnterpriseDB UK: http://www.enterprisedb.com > The Enterprise PostgreSQL Company -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
(2013/05/16 16:22), Dave Page wrote: > Which, btw, means it should really be 09.02.0100, unless we're going > to change the scheme. Now I'm inclined to 9.2.0100. Version 9.2 should have been released before and then the next release would be the last release of 9.2. regards, Hiroshi Inoue
Now that I understand the version history a little better, I'm changing my vote for the next psqlodbc release number to 09.02.0100 . Thanks...jack -- View this message in context: http://postgresql.1045698.n5.nabble.com/Vote-Release-number-of-the-next-tp5755600p5755961.html Sent from the PostgreSQL - odbc mailing list archive at Nabble.com.
Hi. this is a candidate after some discussion's, I will mark in Ver 09.02.0100.! thanks all. Regards, Hiroshi Saito