Re: [boost] [git] automatic ticket closing

Subject: Re: [boost] [git] automatic ticket closing
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2013-12-06 03:53:02

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Lars Viklund
> Sent: Friday, December 06, 2013 8:04 AM
> To: boost_at_[hidden]
> Subject: Re: [boost] [git] automatic ticket closing
> 
> On Thu, Dec 05, 2013 at 04:34:52PM -0700, Cox, Michael wrote:
> > On Thu, Dec 5, 2013 at 9:28 AM, Steven Watanabe <watanabesj_at_[hidden]>wrote:
> > > Patches aren't the only use for attachments.  Test cases are also
> > > common (and absolutely critical).  If the github issue tracker
> > > doesn't support attachments, then it's simply a non-starter.
> > >
> > I'm assuming by the term test cases that means Boost.Test unit-tests.
> 
> A test case as in a minimal piece of end user application code that demonstrates a problem.
> 
> It may be retrofitted into an actual Boost.Test testcase once there is a clear solution to it, but
that's a
> significant burden to put on an end user that just wants to report a bug with reproduction
instructions.
> 
> >  Wouldn't be more convenient to see the modified/new unit-tests for a
> > library code change in the pull-request?
> 
> Convenient, sure. Practically doable by end users unfamiliar with the Boost codebase and
Boost.Test?
> Not really.
> 
> If I'm not wrong, the discussion is about end-user issues as well, not just patch requests.

Definitely.  It's really important that users find it easy to report things - even anonymously.
Adding demos of what is wrong, real test cases, fixes, screen shots... must be *easy*.  Trac is
discouraging enough - the GIT mechanism sounds more intimidating.

Paul

---
Paul A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
[phone]  07714330204
pbristow_at_[hidden]