Subject: Re: [boost] [partly OT] Re: [review queue] What to do about the library review queue?
From: Robert Ramey (ramey_at_[hidden])
Date: 2017-03-16 18:55:21
On 3/16/17 11:01 AM, Stefan Seefeld via Boost wrote:
> On 16.03.2017 13:35, Andrey Semashev via Boost wrote:
>> On 03/16/17 18:01, Peter Dimov via Boost wrote:
>>> Niall Douglas wrote:
>>>> On 16/03/2017 12:10, Vinnie Falco via Boost wrote:
>>>>> On Thu, Mar 16, 2017 at 8:06 AM, Glen Fernandes via Boost
>>>>> <boost_at_[hidden]> wrote:
>>>>>> ...until we truly move to Github Issues
>>>>> What needs to be done in order to make this happen?
>>>> A decision needs to be taken on how best to port the Trac issues into
>>> This implies that we want to port the Trac issues into Github. This is
>>> not a requirement. The 'organic' way to migrate to new things is just to
>>> move on. Trac is legacy; leave it in read-only mode so that history is
>>> preserved, but there's no need to do anything else.
>> If we move to GitHub issues, I would rather have all open tickets
>> moved from Trac there. Leaving them open in read-only Trac is not
>> useful, and you can't request the reporters to duplicate the tickets
>> on GitHub.
>> All open tickets should preferably be in one place.
> Why not let individual project / library maintainers decide how to
> implement the move (or whether they want to move to github issues at all ?)
I think this is a very worthy idea. But I get PRs as well as trac
issues. Hmmm is there a way to diable the PR mechanism on git and just
link to the trac archive?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk