One other point is integrated issue tracking. If someone makes a feature request, we currently manage it purely by not losing the email. With bitbucket issues, users can "follow" issues so when we include "closes #123" (and other status updates) in a commit message, interested users get notified. I know we try to fix all bugs and "good" feature requests within the hour, but there are topics that take longer. projects.html isn't an optimal solution. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120210/b2dc0a11/attachment.html>
- [petsc-dev] petsc-dev on bitbucket Matthew Knepley
- [petsc-dev] petsc-dev on bitbucket Jed Brown
- [petsc-dev] petsc-dev on bitbucket Barry Smith
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Sean Farley
- [petsc-dev] petsc-dev on bitbucket Matthew Knepley
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Matthew Knepley
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Matthew Knepley
- [petsc-dev] petsc-dev on bitbucket Jed Brown
- [petsc-dev] petsc-dev on bitbucket Barry Smith
- [petsc-dev] petsc-dev on bitbucket Jed Brown
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Sean Farley
- [petsc-dev] petsc-dev on bitbucket Sean Farley
- [petsc-dev] petsc-dev on bitbucket Jed Brown
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Sean Farley
- [petsc-dev] petsc-dev on bitbucket Satish Balay
- [petsc-dev] petsc-dev on bitbucket Jed Brown