Re: [HACKERS] BugTracker
[EMAIL PROTECTED] (Peter Eisentraut) writes: Am Mittwoch, 16. August 2006 14:10 schrieb Robert Treat: I'm not sure I follow this, since currently anyone can email the bugs list or use the bugs - email form from the website. Are you looking to increase the barrier for bug reporting? Only a small fraction of the new posts on pgsql-bugs are actually bugs. Most are confused or misdirected users. I don't want to raise that barrier. But I want a higher barrier before something is recorded in the bug tracking system. Seems to me that for there to be a *bit* of a barrier might not be a bad thing... If purported bugs had to be acknowledged before going into the bug tracker system, that wouldn't seem a bad thing. That would mean that the frequent I don't understand what I'm doing and didn't read the documentation reports could be quickly triaged away, which strikes me as an important prerequisite for further automating things. -- select 'cbbrowne' || '@' || 'ntlug.org'; http://cbbrowne.com/info/sap.html FLORIDA: Relax, Retire, Re Vote. ---(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 match
Re: [HACKERS] BugTracker (Was: Re: 8.2 features status)
Kenneth Marshall wrote: RT is easy to setup/configure/use and works well with PostgreSQL as the backend. RT works with Postgres, but I wouldn't say well. All queries in RT are generated by a query generator due to a naive obsession with database independance. They've achieved database independance at the cost of all the queries being brain-dead. Fixing the query generator would be a pretty big job. Drew ---(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 match
Re: [HACKERS] BugTracker (Was: Re: 8.2 features status)
Kenneth Marshall wrote: RT is easy to setup/configure/use and works well with PostgreSQL as the backend. RT works with Postgres, but I wouldn't say well. All queries in RT are generated by a query generator due to a naive obsession with database independance. They've achieved database independance at the cost of all the queries being brain-dead. Fixing the query generator would be a pretty big job. We use RT with PostgreSQL for all internal IT requests and development/support/doc tasks on a couple products, and there's never been a problem. Are the queries optimal? no. The alternative might have been MySQL-only, and that would be worse. I can't really give a fair estimate on performance, because I'm running it on a PIII at 800MHz with several other things as well. But it's fast enough that I'm not screaming for a hardware upgrade. Regards, Paul Bort ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] BugTracker (Was: Re: 8.2 features status)
Did you look at http://www.atlassian.com/software/jira/ - can use postgresql as database - free to open source projects, used by apache, hiberate, OpenSymphony - bugs may be submitted via email/web - built-in configurable workflow - runs as J2EE webapp on a number of OS's - lots of other features I am not associated with the company, just a user. ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
Re: [HACKERS] BugTracker (Was: Re: 8.2 features status)
[EMAIL PROTECTED] wrote: Did you look at http://www.atlassian.com/software/jira/ We had discussed that in an earlier round, but it's not free software, so it's out of the question. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(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 match
Re: [HACKERS] BugTracker
On Wed, Aug 16, 2006 at 11:12:11AM +0800, Christopher Kings-Lynne wrote: Trac does support PostgreSQL... The thing I don't understand at this point is what exactly is the nature of the integration with the SCM. I don't see it being likely that there will be a deep integration of the PostgreSQL SCM (whatever the SCM platform) with Trac; that's way too much change to expect quickly... Basically I have it set up like this: * Trac has built-in browsing of the svn via the web * When I commit, the commit message must have a reference to an open ticket in Trac, eg: Rearrange blah to fix bad bug. Fixes #745 * In trac's development timeline, or whatever you can see all the commits against each ticket, and just click on them to see the complete diff for each change set in SVN. * Commit messages can contain full wiki markup, that fully integrates with the wiki that is all thoughout Trac. So, you can have wiki in your commit messages that refers to other bugs, wiki pages, source code files and lines, etc. Basically, Trac is cool. I don't see us adopting it too quickly for PostgreSQL though :P Well, CMD does have it up and running with our repository as sucked out of CVS. Granted, not full functionality, but better than nothing. If Josh turns on the rest of the stuff folks could go play with it and see what they think. BTW, if GNATS is what FreeBSD uses I'd have to agree that it's pretty ugly. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.comwork: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] BugTracker
In an attempt to throw the authorities off his trail, ler@lerctr.org (Larry Rosenman) transmitted: I've used and use RT. It is web based for admin, but all the transactions are E-Mail based. http://www.bestpractical.com I can also make a test queue on my instance if someone wants to play. We've got an RT system at work where some queues are set up to be sorta email manageable. I see in their docs a CommandByMail extension that allows doing such things via email request as: - changing queue - setting status, custom fields - assigning owners, watchers, links It's not self-evident what the security implications are; I'm not sure how requests are authenticated. -- (reverse (concatenate 'string moc.liamg @ enworbbc)) http://linuxfinances.info/info/finances.html As of next month, MACLISP / will be flushed in favor of \. Please update the WORLD. ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] BugTracker
Martha Stewart called it a Good Thing when [EMAIL PROTECTED] (Christopher Kings-Lynne) wrote: We have three candidates already -- debbugs, RT and Gnats. The first has the advantage that was written by hackers, for hackers, so it doesn't have any of the insane for end users stuff which annoys so many people around here ;-) (On the other hand it does have some web stuff for generating reports, etc). Kill me now if I have to use GNATS :) Have you ever tried submitting a bug to the FreeBSD project? *shudder* That said, I'll live :) I have recently totally falling in love with Trac and its complete subversion integration. I'm not sure it supports PostgreSQL, and converting to subversion is probably a little too hardcore at the moment :) Trac does support PostgreSQL... The thing I don't understand at this point is what exactly is the nature of the integration with the SCM. I don't see it being likely that there will be a deep integration of the PostgreSQL SCM (whatever the SCM platform) with Trac; that's way too much change to expect quickly... -- (reverse (concatenate 'string ofni.secnanifxunil @ enworbbc)) http://linuxdatabases.info/info/spreadsheets.html Any programmer who fails to comply with the standard naming, formatting, or commenting conventions should be shot. If it so happens that it is inconvenient to shoot him, then he is to be politely requested to recode his program in adherence to the above standard. -- Michael Spier, Digital Equipment Corporation ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] BugTracker
Trac does support PostgreSQL... The thing I don't understand at this point is what exactly is the nature of the integration with the SCM. I don't see it being likely that there will be a deep integration of the PostgreSQL SCM (whatever the SCM platform) with Trac; that's way too much change to expect quickly... Basically I have it set up like this: * Trac has built-in browsing of the svn via the web * When I commit, the commit message must have a reference to an open ticket in Trac, eg: Rearrange blah to fix bad bug. Fixes #745 * In trac's development timeline, or whatever you can see all the commits against each ticket, and just click on them to see the complete diff for each change set in SVN. * Commit messages can contain full wiki markup, that fully integrates with the wiki that is all thoughout Trac. So, you can have wiki in your commit messages that refers to other bugs, wiki pages, source code files and lines, etc. Basically, Trac is cool. I don't see us adopting it too quickly for PostgreSQL though :P Chris ---(end of broadcast)--- TIP 6: explain analyze is your friend
