I would be perfectly happy to have a "bug database" for PETSc but I demand that it match our current workflow. I do not want to switch to some crappy webbased bug reporting system that both the developers and users hate. No one has yet demonstrated a "bug database" system that would match our current workflow.*
I totally agree "that it is actually useful to users to be able to watch bugs or feature requests without the high volume of following petsc-dev or reading the Hg commit log to get news of action on it." this would be fantastic to have. Unfortunately the current tradeoff with proposed solutions is too high. Barry For example if you have some demon that tracks petsc-users, petsc-dev, and petsc-maint and collects the relevant information in a web database that would be utterly fantastic. On Apr 25, 2012, at 4:35 PM, Jed Brown wrote: > On Wed, Apr 25, 2012 at 16:27, Sou-Cheng (Terrya) Choi <sctchoi at > uchicago.edu> wrote: > Hi Jed, > > May I ask where I could search for issues and maybe file bugs for the > development version of PETSc? Are there any "bug database" where I could > check the status, work-around, warnings/errors, etc? Thanks! > > Barry doesn't believe in having a place to keep track of this stuff because > he thinks it causes bug reports to be closed prematurely or allows bugs to go > too long without being fixed. So we discuss this stuff on petsc-dev or > petsc-maint and it sits in our inboxes until someone fixes it. > > Every once in a while, Barry reiterates his contempt for bug trackers and I > reiterate my perspective that it is actually useful to users to be able to > watch bugs or feature requests without the high volume of following petsc-dev > or reading the Hg commit log to get news of action on it. ;-) > > > There is this list of projects. > > http://www.mcs.anl.gov/petsc/developers/projects.html
