Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years

Subject: Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
From: Daniel Pfeifer (daniel_at_[hidden])
Date: 2014-12-31 08:08:06

On Wed, Dec 31, 2014 at 11:44 AM, Gennadiy Rozental <rogeeff_at_[hidden]>
wrote:

> ... what I was after is something different. I want
> to fix the ticket with actual commit and than in a commit which brings
> changes from develop to master I do not really want to remember which
> tickets this fixes/addresses (especially since I might be doing it half a
> year later with potentially dozen or more fixes bundled together).

GitHub supports that workflow: When you mark an issue as solved from a
commit message, that commit is added as a comment to the issue. The issue
itself is closed as soon as the change is merged to master.

This even works across forks! Say, I fork your repository, fix some issues
and push them to my fork. You will see a comment on the issue that my fork
contains the fixes. When you merge the changes into the develop branch of
your repository, another comment is added to the issue. Once you merge to
master, the issue is closed.

Maybe it is time to leave trac behind?