Bug summary
__
Summary for 2017-09-24 through 2017-10-01
Opened Closed Total Change
Enhancements: 2 1 1366 +1
Defects: 9 4895 +5
Tasks: 0 0 9
On Sat, Sep 30, 2017 at 2:15 PM, Adi Roiban wrote:
> Hi,
>
> I would like to re-start the conversation about migrating Trac tickets
> to GitHub issues.
>
> My main reason for doing this is to make it easier for people to
> contribute to Twisted.
>
I think migrating Twisted issues from Trac to G
I am restarting this discussion
https://twistedmatrix.com/pipermail/twisted-python/2016-May/030333.html
I am starting a new thread since I want to keep the focus on the
review process / workflow / markers, and not on the things required to
accept a PR or do a review.
--
> Proposing: Just
On 30 September 2017 at 22:15, Adi Roiban wrote:
[snip]
>
>
> Below are the things that I things we will lose when migrating to
> GitHub Issues and which will require extra work.
>
[snip]
6. We will no longer get the tickets pending review reported on IRC.
Beside reimplementing this
Hi,
I would like to re-start the conversation about migrating Trac tickets
to GitHub issues.
My main reason for doing this is to make it easier for people to
contribute to Twisted.
In CONTRIBUTING there is this info
`GitHub doesn't provide adequate tooling for its community.`
I don't know what
