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: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2014-12-30 02:38:44

Tim Blechmann <tim <at> klingt.org> writes:

> b) 'blanked update messages' about anything that is done on an a develop
> branch, is useless for people who are submitting 
> and/or watching tickets.

When one is expected to close the ticket? When fix is checked into devel or 
when fix is merges into master? Former is better for developer who can put 
the trac number into commit message and be done with it. Later is better 
for users, since there always will be some gap between commit and master 
merge. Yet it requires more effort/discipline from developer. I am not 
convinced which one is better. Maybe we can mark ticket as fixed at commit 
time, and make it merged/publically available when fix is merged to master. 
Can we tweak trac/svn hooks so that we introduce another state change?

> if for whatever reason you are not able to maintain boost.test or cannot
> devote any time on this, you might want to accept help from others.

For various reasons, what needs to be done here seriously exceed the volume 
of regular maintenance, which I am fine with. Thus the delay. That said I 
did ask for help with this work. One person replied and we are working on 
making this happen. Now it seems more people are interested, so I can be 
somewhat positive on claiming that you should see real process soon.

Gennadiy