Alpha release this week?
in [PgSql]
|
Prev: [HACKERS] five-key syscaches
Next: [HACKERS] GSoC Query
From: Josh Berkus on 30 Mar 2010 16:43 On 3/29/10 5:04 PM, Magnus Hagander wrote: > Last i heard from Dave on that topic is that there's no chance of that > happening that quickly. He's on a plane now but I'm sure he'll confirm > that when he lands. That means that we'll be doing the test-fest using Alpha4, materially. Which is annoying because it means we'll be catching a lot of bugs which are already fixed. However, it's pretty much impossible for me to coordinate 25 volunteers getting the *same* daily snapshot. And we need to test on Windows, since it has all kinds of special issues. I think my big goal for 9.1 is going to be to fix our testing procedure, or rather total lack of a procedure. We've got development systematized, now it's time for testing. I'm just sorry that the press of work kept me from really doing it this time around. I think we could be getting from alpha to beta in 6 weeks if we actually had a schedule and some real testing goals. -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Robert Haas on 30 Mar 2010 18:01 On Tue, Mar 30, 2010 at 4:43 PM, Josh Berkus <josh(a)agliodbs.com> wrote: > On 3/29/10 5:04 PM, Magnus Hagander wrote: >> Last i heard from Dave on that topic is that there's no chance of that >> happening that quickly. He's on a plane now but I'm sure he'll confirm >> that when he lands. > > That means that we'll be doing the test-fest using Alpha4, materially. > Which is annoying because it means we'll be catching a lot of bugs which > are already fixed. However, it's pretty much impossible for me to > coordinate 25 volunteers getting the *same* daily snapshot. And we need > to test on Windows, since it has all kinds of special issues. > > I think my big goal for 9.1 is going to be to fix our testing procedure, > or rather total lack of a procedure. We've got development > systematized, now it's time for testing. I'm just sorry that the press > of work kept me from really doing it this time around. > > I think we could be getting from alpha to beta in 6 weeks if we actually > had a schedule and some real testing goals. At the risk of being blunt, AFAICT, the delay in getting to beta has little or nothing to do with testing and everything to do with the fact that streaming replication got committed with a long list of open items two months ago, and many of them haven't been fixed yet. Hot Standby has a few warts too, but I think Simon has done a better job cleaning up the loose ends there (with help from Tom and Heikki), no doubt because he got it committed two months sooner than SR. From a project management point of view, it seems to me that we shouldn't commit major patches late in the release cycle unless someone has the time to actually get them finished and stable. If Streaming Replication were any other patch, we would have reverted it a month ago. As it is, it looks like we're going to be waiting until Heikki has time to deal with the issues, because it doesn't look like any of the other committers are able/willing to help. ....Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Fujii Masao on 30 Mar 2010 22:32 On Wed, Mar 31, 2010 at 7:01 AM, Robert Haas <robertmhaas(a)gmail.com> wrote: > At the risk of being blunt, AFAICT, the delay in getting to beta has > little or nothing to do with testing and everything to do with the > fact that streaming replication got committed with a long list of open > items two months ago, and many of them haven't been fixed yet. Hot > Standby has a few warts too, but I think Simon has done a better job > cleaning up the loose ends there (with help from Tom and Heikki), no > doubt because he got it committed two months sooner than SR. From a > project management point of view, it seems to me that we shouldn't > commit major patches late in the release cycle unless someone has the > time to actually get them finished and stable. If Streaming > Replication were any other patch, we would have reverted it a month > ago. As it is, it looks like we're going to be waiting until Heikki > has time to deal with the issues, because it doesn't look like any of > the other committers are able/willing to help. I believe that anyone except Heikki & me can deal with the following issues since they started with SR but actually are not tied up to SR ;) * dblink and walreceiver are not interruptible on win32 http://archives.postgresql.org/pgsql-hackers/2010-01/msg01672.php http://archives.postgresql.org/pgsql-hackers/2010-03/msg00413.php * smart shutdown during recovery gets stuck http://archives.postgresql.org/pgsql-hackers/2010-01/msg02044.php http://archives.postgresql.org/pgsql-hackers/2010-03/msg01208.php * pg_xlogfile_name() might report the wrong name http://archives.postgresql.org/pgsql-hackers/2010-01/msg01806.php Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Stefan Kaltenbrunner on 31 Mar 2010 01:57 Josh Berkus wrote: > On 3/29/10 5:04 PM, Magnus Hagander wrote: >> Last i heard from Dave on that topic is that there's no chance of that >> happening that quickly. He's on a plane now but I'm sure he'll confirm >> that when he lands. > > That means that we'll be doing the test-fest using Alpha4, materially. > Which is annoying because it means we'll be catching a lot of bugs which > are already fixed. However, it's pretty much impossible for me to > coordinate 25 volunteers getting the *same* daily snapshot. And we need > to test on Windows, since it has all kinds of special issues. well this is actually the first release cycle where we even HAD alpha releases - as for the snapsho thing I cannot see why you could not download a snpashot on your own, put it somewhere (like a wiki page) and send out an email to all the volunteers and ask them to use at least that one if building from source... Stefan -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Dave Page on 31 Mar 2010 03:57
On Tue, Mar 30, 2010 at 1:04 AM, Magnus Hagander <magnus(a)hagander.net> wrote: > Last i heard from Dave on that topic is that there's no chance of that > happening that quickly. He's on a plane now but I'm sure he'll confirm that > when he lands. Not with any amount of testing as we'd normally give any build before releasing it anyway. I can certainly stuff a tarball into the new build machine and see what comes out the next morning. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |