-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Peter Dimov via Boost Sent: 16 March 2017 17:28 To: boost@lists.boost.org Cc: Peter Dimov Subject: Re: [boost] [partly OT] Re: [review queue] What to do about the library review queue?
Paul A. Bristow wrote:
From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Vinnie Falco via Boost Here's an alternative, lock Trac so no new issues can be created, inform users they should open new issues using GitHub, then fix all the open issues remaining on Trac so there's nothing to port :)
That might be a bit nuclear - what about all the outstanding issues and discussions in the process of being fixed?
Vinnie's suggestion is to disable new issue creation; outstanding issues will remain unaffected. It was I who proposed putting it all on read-only. :-)
PS How should we reference GitHub discussions in 'history' documentation so that I (and the search engines) can find them? The equivalent of, for example, https://svn.boost.org/trac/boost/ticket/12908).
Not sure about search engines.
Ah well that's a big issue - I've found it very useful to find links to questions that I've asked and had answered a couple of years previously several times ;-) Eyes passim as they say in Private Eye :-(
For references, don't links to Github work fine? F.ex. https://github.com/boostorg/build/issues/168
Well, I could not find this particular one but it is newish and hard to find unique search terms, but others came up, so I think the bots are indexing OK. Are others confident from experience that searching does work? I doubt if moving tickets will be worth the effort (since it is in such short supply ;-). I'd prefer the cheapest most organic method of just saying on the Boost site that the way to report issues is now to use github. Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830