[petsc-dev] petsc-dev on bitbucket

[Jed Brown]

On Fri, Feb 10, 2012 at 11:30, Barry Smith <bsmith at mcs.anl.gov> wrote:

> On Feb 10, 2012, at 11:26 AM, Jed Brown wrote:
>
> > 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.
>
>   Like Barry is ever going to remember to write closes #123 in a commit
> message :-(


The rest of us that read the commit logs can still mark the issue as closed
afterward (so people following it get notified).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120210/5010bac9/attachment.html>