Thread: New minor release?
Hi, I was wondering if we'll get out a new minor release. We already have 18 fixes in 1.10 branch, and another two remaining to be fixed. I'm working on one of them (http://code.pgadmin.org/trac/ticket/38), but I'm having a hard time to fix it. Anyways, as PostgreSQL will soon have minor releases out, is it planned for pgAdmin too? -- Guillaume. http://www.postgresqlfr.org http://dalibo.com
On Thu, Sep 3, 2009 at 12:20 PM, Guillaume Lelarge<guillaume@lelarge.info> wrote: > Hi, > > I was wondering if we'll get out a new minor release. We already have 18 fixes > in 1.10 branch, and another two remaining to be fixed. I'm working on one of > them (http://code.pgadmin.org/trac/ticket/38), but I'm having a hard time to > fix it. > > Anyways, as PostgreSQL will soon have minor releases out, is it planned for > pgAdmin too? PostgreSQL's are being released tomorrow - there's zero chance of doing 1.10.1 before then. I was hoping to get a bunch of Solaris fixes into 1.10.1. I've got some in so far, but the majority seem to be sparc-specific, so I've had to order some hardware which hasn't arrived yet :-( Are there any fixes in there that re worthy of forcing a release? We don't normally schedule one based on the number of changes, but on the overall severity/impact. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Thu, Sep 3, 2009 at 13:31, Dave Page<dpage@pgadmin.org> wrote: > On Thu, Sep 3, 2009 at 12:20 PM, Guillaume > Lelarge<guillaume@lelarge.info> wrote: >> Hi, >> >> I was wondering if we'll get out a new minor release. We already have 18 fixes >> in 1.10 branch, and another two remaining to be fixed. I'm working on one of >> them (http://code.pgadmin.org/trac/ticket/38), but I'm having a hard time to >> fix it. >> >> Anyways, as PostgreSQL will soon have minor releases out, is it planned for >> pgAdmin too? > > PostgreSQL's are being released tomorrow - there's zero chance of > doing 1.10.1 before then. > > I was hoping to get a bunch of Solaris fixes into 1.10.1. I've got > some in so far, but the majority seem to be sparc-specific, so I've > had to order some hardware which hasn't arrived yet :-( > > Are there any fixes in there that re worthy of forcing a release? We > don't normally schedule one based on the number of changes, but on the I think there are a bunch of them leading up to it being reasonable for a new release. However, if we can't make the timing of the postgresql one (which is a wrap tomorrow - not a realease - but the wrap is really what matters), we can delay it for a couple of weeks just as well - especially if we have more fixes currently being worked on. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Le jeudi 3 septembre 2009 à 13:35:10, Magnus Hagander a écrit : > On Thu, Sep 3, 2009 at 13:31, Dave Page<dpage@pgadmin.org> wrote: > > On Thu, Sep 3, 2009 at 12:20 PM, Guillaume > > > > Lelarge<guillaume@lelarge.info> wrote: > >> Hi, > >> > >> I was wondering if we'll get out a new minor release. We already have 18 > >> fixes in 1.10 branch, and another two remaining to be fixed. I'm working > >> on one of them (http://code.pgadmin.org/trac/ticket/38), but I'm having > >> a hard time to fix it. > >> > >> Anyways, as PostgreSQL will soon have minor releases out, is it planned > >> for pgAdmin too? > > > > PostgreSQL's are being released tomorrow - there's zero chance of > > doing 1.10.1 before then. > > > > I was hoping to get a bunch of Solaris fixes into 1.10.1. I've got > > some in so far, but the majority seem to be sparc-specific, so I've > > had to order some hardware which hasn't arrived yet :-( > > > > Are there any fixes in there that re worthy of forcing a release? We > > don't normally schedule one based on the number of changes, but on the > > I think there are a bunch of them leading up to it being reasonable > for a new release. However, if we can't make the timing of the > postgresql one (which is a wrap tomorrow - not a realease - but the > wrap is really what matters), we can delay it for a couple of weeks > just as well - especially if we have more fixes currently being worked > on. Delaying would be probably good enough if we can put some more fixes in it. We know there are at least one ticket opened for all platform, one other for linux platform and a few bugs sparc-specific. So, +1 for the delay. Magnus, can you get a look at "Savepoints in PgAdmin" thread on pgadmin- support? I would like to have your point of view on this. Thanks. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com
Dave Page píše v čt 03. 09. 2009 v 12:31 +0100: > On Thu, Sep 3, 2009 at 12:20 PM, Guillaume > Lelarge<guillaume@lelarge.info> wrote: > > Hi, > > > > I was wondering if we'll get out a new minor release. We already have 18 fixes > > in 1.10 branch, and another two remaining to be fixed. I'm working on one of > > them (http://code.pgadmin.org/trac/ticket/38), but I'm having a hard time to > > fix it. > > > > Anyways, as PostgreSQL will soon have minor releases out, is it planned for > > pgAdmin too? > > PostgreSQL's are being released tomorrow - there's zero chance of > doing 1.10.1 before then. > > I was hoping to get a bunch of Solaris fixes into 1.10.1. I've got > some in so far, but the majority seem to be sparc-specific, so I've > had to order some hardware which hasn't arrived yet :-( Do you have any list? Unfortunately, I'm not able to monitor pgadmin development much :(. I will look what I can do. I think that I could find some sparc machine here ;-). Zdenek
On Fri, Sep 4, 2009 at 4:27 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote: > > Do you have any list? Unfortunately, I'm not able to monitor pgadmin > development much :(. I will look what I can do. I think that I could > find some sparc machine here ;-). :-) They're all ones that our QA team in EDB have found, so they're currently in our internal ticketing system. Not entirely sure how I can get them out of that easily, with all the details - I'll see what I can figure out. FYI, I have a remanufactured Blade 2000 on order, but it's going to be another couple of weeks yet. Getting hold of a SPARC workstation isn't so easy these days - all you guys seem to sell now is higher-end rack mount servers with SPARC chips. The cheaper stuff is all x86_64. Thanks. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Fri, Sep 4, 2009 at 4:30 PM, Dave Page<dpage@pgadmin.org> wrote: > On Fri, Sep 4, 2009 at 4:27 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote: >> >> Do you have any list? Unfortunately, I'm not able to monitor pgadmin >> development much :(. I will look what I can do. I think that I could >> find some sparc machine here ;-). > > :-) > > They're all ones that our QA team in EDB have found, so they're > currently in our internal ticketing system. Not entirely sure how I > can get them out of that easily, with all the details - I'll see what > I can figure out. Hmm, not much unfortunately, so I dumped most of them manually to the new tracker (http://code.pgadmin.org/). Just to give a little background and info in case I missed editting any of the details: - All of these came from the EDB QA team, who were testing the build we'll ship with Advanced Server 8.3R2. - If you see any mention of 'Postgres Studio', substitute pgAdmin. The code is identical for this release. - The builds the QA team were testing are from our change management (CM) team. I believe they were using the Sun Studio compiler. At one point they were also using a custom build of GTK to work around some nasty bugs, the details of which escape me at present. - Some of the responses (normally along the lines of 'I can't reproduce this on S10/x86_64) came from me. I was testing my own builds, and using GCC 'cos I can't get wxWidgets to compile with the latest Sun Studio. - Most of these issues seem to be Sparc specific, and some are Solaris 9 specific (mainly the sizing related ones I think). I was going to give these more attention when my hardware turns up, but if you can knock any off, or show they are something specific to CM's build/environment that'd be most helpful. In any case, all of these potentially affect community users, so I'd like to clear out as many as possible before 1.10.1. Thanks! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page píše v pá 04. 09. 2009 v 17:27 +0100: > > Just to give a little background and info in case I missed editting > any of the details: > > - All of these came from the EDB QA team, who were testing the build > we'll ship with Advanced Server 8.3R2. > > - If you see any mention of 'Postgres Studio', substitute pgAdmin. The > code is identical for this release. I try it on latest Nevada build and I'm not able to reproduce. Some bugs seems are related to the Advanced Server which I don't have installed. And of course I don't have Chines keyboard ;-). > - The builds the QA team were testing are from our change management > (CM) team. I believe they were using the Sun Studio compiler. At one > point they were also using a custom build of GTK to work around some > nasty bugs, the details of which escape me at present. It is good to know that GCC on Sparc is buggy and slow. I seen also that some issue are reported on old S10 version. You should retest it on latest version of S10 which is update 7. At least S10U4 contains libxml which is required. > - Some of the responses (normally along the lines of 'I can't > reproduce this on S10/x86_64) came from me. I was testing my own > builds, and using GCC 'cos I can't get wxWidgets to compile with the > latest Sun Studio. You can look http://src.opensolaris.org/source/xref/sfw/usr/src/lib/wxwidgets/ We build it with the latest SUN Studio. For S10 we used older Sun Studio. Both works fine as well. > - Most of these issues seem to be Sparc specific, and some are Solaris > 9 specific (mainly the sizing related ones I think). Are they sparc specific because you don't have x86 Solaris 9 or does it really problem on the Sparc build. > I was going to give these more attention when my hardware turns up, > but if you can knock any off, or show they are something specific to > CM's build/environment that'd be most helpful. In any case, all of > these potentially affect community users, so I'd like to clear out as > many as possible before 1.10.1. You can see how pgadmin is built on Solaris. I commit 1.10 today and it should be visible tomorrow http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/postgres/pgadmin/ Zdenek
On Fri, Sep 4, 2009 at 8:21 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote: > I try it on latest Nevada build and I'm not able to reproduce. Some bugs > seems are related to the Advanced Server which I don't have installed. Understood. > And of course I don't have Chines keyboard ;-). Copy 'n' paste is your friend :-) >> - The builds the QA team were testing are from our change management >> (CM) team. I believe they were using the Sun Studio compiler. At one >> point they were also using a custom build of GTK to work around some >> nasty bugs, the details of which escape me at present. > > It is good to know that GCC on Sparc is buggy and slow. I seen also that > some issue are reported on old S10 version. You should retest it on > latest version of S10 which is update 7. At least S10U4 contains libxml > which is required. Right - but our customers run older versions too, so we try to test a range. > You can look > http://src.opensolaris.org/source/xref/sfw/usr/src/lib/wxwidgets/ > We build it with the latest SUN Studio. For S10 we used older Sun > Studio. Both works fine as well. Hmm - I ran into some macro conflicts when I tried. I found some emails about the same on the wxWidgets list, which basically said there are conflicts with the latest headers from Sun Studio - from what I could gather this was to be fixed in wxWidgets 3.x, but in the meantime, the answer was to use an older Sun Studion (which I couldn't find for download) or GCC. I'll see if I can get a good build based on the opensolaris makefile. >> - Most of these issues seem to be Sparc specific, and some are Solaris >> 9 specific (mainly the sizing related ones I think). > > Are they sparc specific because you don't have x86 Solaris 9 or does it > really problem on the Sparc build. Well some are Sparc 9 & 10, but not x86 Solaris 10. We don't support x86 Solaris 9 so haven't tested that. >> I was going to give these more attention when my hardware turns up, >> but if you can knock any off, or show they are something specific to >> CM's build/environment that'd be most helpful. In any case, all of >> these potentially affect community users, so I'd like to clear out as >> many as possible before 1.10.1. > > You can see how pgadmin is built on Solaris. I commit 1.10 today and it > should be visible tomorrow > http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/postgres/pgadmin/ I can only see 1.8 there - but the Makefile is there of course, which may be useful. Thanks! -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page píše v po 07. 09. 2009 v 10:09 +0100: > On Fri, Sep 4, 2009 at 8:21 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote: > > > I try it on latest Nevada build and I'm not able to reproduce. Some bugs > > seems are related to the Advanced Server which I don't have installed. > > Understood. > > > And of course I don't have Chines keyboard ;-). > > Copy 'n' paste is your friend :-) > > >> - The builds the QA team were testing are from our change management > >> (CM) team. I believe they were using the Sun Studio compiler. At one > >> point they were also using a custom build of GTK to work around some > >> nasty bugs, the details of which escape me at present. > > > > It is good to know that GCC on Sparc is buggy and slow. I seen also that > > some issue are reported on old S10 version. You should retest it on > > latest version of S10 which is update 7. At least S10U4 contains libxml > > which is required. > > Right - but our customers run older versions too, so we try to test a range. the question if it is appear only on older S10 updates or on all. You can try apply xml patches on S10U3 and try it again. > > You can look > > http://src.opensolaris.org/source/xref/sfw/usr/src/lib/wxwidgets/ > > We build it with the latest SUN Studio. For S10 we used older Sun > > Studio. Both works fine as well. > > Hmm - I ran into some macro conflicts when I tried. I found some > emails about the same on the wxWidgets list, which basically said > there are conflicts with the latest headers from Sun Studio - from > what I could gather this was to be fixed in wxWidgets 3.x, but in the > meantime, the answer was to use an older Sun Studion (which I couldn't > find for download) or GCC. Yeah, I hit this problem as well. At this moment some build machine uses old SS12 version and some new one (I tested it with old compiler version), but next month all is going to switch to the latest one. I need it fixed asap, else new pgAdmin will be removed from Solaris :(. See http://trac.wxwidgets.org/ticket/10660 The problem is with _T macro which has conflict with STL. something like #undef _T in pgAdmin sources should help. I will look on it and I hope send patch soon. > I'll see if I can get a good build based on the opensolaris makefile. Probably not if you have new compiler :(. > >> - Most of these issues seem to be Sparc specific, and some are Solaris > >> 9 specific (mainly the sizing related ones I think). > > > > Are they sparc specific because you don't have x86 Solaris 9 or does it > > really problem on the Sparc build. > > Well some are Sparc 9 & 10, but not x86 Solaris 10. We don't support > x86 Solaris 9 so haven't tested that. I guess that Solaris 9 only bug is mostly GTK problem on Solaris 9 not Sparc specific, but who knows. > >> I was going to give these more attention when my hardware turns up, > >> but if you can knock any off, or show they are something specific to > >> CM's build/environment that'd be most helpful. In any case, all of > >> these potentially affect community users, so I'd like to clear out as > >> many as possible before 1.10.1. > > > > You can see how pgadmin is built on Solaris. I commit 1.10 today and it > > should be visible tomorrow > > http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/postgres/pgadmin/ > > I can only see 1.8 there - but the Makefile is there of course, which > may be useful. Hmm, I don't know how often it is regenerated. I guess that it should appear soon. Zdenek
On Mon, Sep 7, 2009 at 8:37 PM, Zdenek Kotala<Zdenek.Kotala@sun.com> wrote: > > Yeah, I hit this problem as well. At this moment some build machine uses > old SS12 version and some new one (I tested it with old compiler > version), but next month all is going to switch to the latest one. I > need it fixed asap, else new pgAdmin will be removed from Solaris :(. > See http://trac.wxwidgets.org/ticket/10660 > > The problem is with _T macro which has conflict with STL. something like > #undef _T in pgAdmin sources should help. I will look on it and I hope > send patch soon. Ahh yes, that's exactly what I ran into. Patching pgAdmin alone doesn't help me much though - it's wxWidgets I can't build and I cannot download the older compiler from anywhere :-( > I guess that Solaris 9 only bug is mostly GTK problem on Solaris 9 not > Sparc specific, but who knows. A number of the bugs reported look like they may all have one root cause - namely that a combo box is not firing an item selected event, which may well be GTK. That results in problems like selecting a column to add to an index, but the 'Add' button remaining disabled. On the plus side - I just had a call that my sparc box is going to arrive earlier than expected; this Thursday :-) -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com