> On 25 Apr 2018, at 5:46 pm, Ryan Schmidt <[email protected]> wrote:
> 
> 
>> On Apr 25, 2018, at 11:31, Chris Jones wrote:
>> 
>> Personally, I would like to see MacPorts go in exactly the opposite 
>> direction, so migrate away from using trac for anything much. I also happen 
>> to think, one way or another this will naturally happen as people get used 
>> to, and see all the advantages, of doing everything within github...
> 
> When we switched to GitHub, we spent a lot of time considering whether to 
> move our Trac tickets to GitHub Issues. Smaller macOS forge projects were 
> happy with that change, but after careful consideration, we came to the 
> conclusion that GitHub Issues did not have as many features as Trac and would 
> make it more difficult for us to accomplish our work. I'm not aware of GitHub 
> Issues having gained new features since then, such that I don't think our 
> decision would be different today.

Thats fine, but not what i am talking about. If someone starts an update, in a 
branch in github but reaches a point where it is not quite done, but wishes to 
discuss it with reviewers, it makes infinite more sense to submit that as a WIP 
MR instead of converting it to a patch and submitting that to trac. That, 
frankly, would be absurb.

Chris

> 
> If we do want to convert our Trac tickets to GitHub Issues, I still have the 
> conversion scripts I prepared at that time.
> 

Reply via email to