Tue Oct 16 12:54:22 PDT 2007
- Previous message: [Slony1-general] Making one system a master in respect of some replication set, but a slave in respect of another
- Next message: [Slony1-general] Bug Tracking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
One thing that seems to have fallen by the wayside in the migration from gBorg to the nice new digs of main.slony.info at Command Prompt is the bug tracker. We used to have the gBorg bug tracker; there is not now any tooling to help support tracking bugs. I have been getting pestered by some community members about this, as the statuses of some of the issues that have come up in the v1.2 branch have not been totally obvious. Way Back When, we were talking about the migration from gBorg to the new site, there was some enthusiasm over using a Bugzilla instance at Command Prompt, which seems still to be there at <http://pgbugs.commandprompt.com/>. Is that still something that people would be enthusiastic about? I think activating it would take some (hopefully small?) amount of effort on Command Prompt's part... -- let name="cbbrowne" and tld="linuxdatabases.info" in String.concat "@" [name;tld];; http://linuxfinances.info/info/lisp.html C program run -- Run program run -- Run, C program, Run! -- (please)
- Previous message: [Slony1-general] Making one system a master in respect of some replication set, but a slave in respect of another
- Next message: [Slony1-general] Bug Tracking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list