I am writing here to get some feedback about migration Twisted Trac
Ticket to GitHub Issues.
In short, try to spend more time doing Twisted development and less
time developing custom tools and doing sysadmin work.
The main reason for the migration is that we don't have enough
people/time to manage the Trac instance or improve the dev tools
With GitHub issues it should be easier to reuse tools created by
others for GitHub.
Also, I think that having Pull Requests an GitHub with the GitHub own
review queue/report and a separate set of report in Trac is extra
We are already doing Trac authentication via Github.
Anyone over here who is against migrating the Twisted Trac tickets to GitHub ?
I see Trac has about 10300 tickets and GitHub PR is now at 1672 .
We can migrate with keeping the same ID for the majority of the tickets.
With the migration the original author of a ticket/comment is lost.
This is a security feature in GitHub.
Also, it's not trivial to get all the Trac accounts mapped to GitHub accounts.
We can keep the existing Trac in read-only mode for some time.
And it can (and will be) linked from Github Issues
For the attachments, they can be hosted on a static HTTP site like
`trac-attachments.twisted.org` (which can be hosted by Github pages)
and linked from GitHub Issues.
Components, Priority, and keywords can be converted to GitHub Issue labels.
"Owned by" can be converted to GitHub issue assignee ... if we have a mapping :)
The milestones can be converted to GitHub Issue milestones
"Branch" trac ticket custom field can be used to detect a link to a GitHub PR
Until recently the Twisted Trac instance was running on Ubuntu 16.04
... and I don't know how often it is updated.
Now, Trac is hosted on an Azure VM with Ubuntu 20.04... but we don't
have time to look after it.
If the majority of Twisted devs agree to migrate to GitHub we can look
into the execution details.
My company has recently migrated from Trac to GitHub and I can ask my
colleague to help with the Twisted migration.
PS: later we can also look at migrating the Trac Wiki to GitHub Wiki
PS: there is also planning to have a simpe (static) presentation site
for Twisted https://github.com/twisted/twisted.github.io/pull/6 .. to
replace the current site that is hosted via Trac Wiki with heavy
Trying to create a new issue gave:
==== How to Reproduce ====
While doing a POST operation on `/newticket`, Trac issued an internal error.
''(please provide additional details here)''
twisted.trial.unittest import TestCase\r\n\r\n\r\nclass
StatefulCleanup:\r\n\r\n called = False\r\n\r\n def
__call__(self):\r\n if self.called:\r\n raise
AssertionError('Called more than once')\r\n self.called =
True\r\n\r\n\r\nclass TestAddCleanup(TestCase):\r\n\r\n def
setUp(self):\r\n self.addCleanup(StatefulCleanup())\r\n\r\n def
testIt(self):\r\n pass\r\n}}}\r\n\r\n\r\nIf run with trial -u,
the AssertionError will be issued.",
u'field_summary': u'Cleanups added with addCleanup incorrectly called
on subsequent runs when using `trial -u`',
u'submit': u'Create ticket'}
User agent: `Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36`
==== System Information ====
''System information not available''
==== Enabled Plugins ====
''Plugin information not available''
==== Interface Customization ====
''Interface customization information not available''
==== Python Traceback ====
Traceback (most recent call last):
line 623, in _dispatch_request
line 239, in dispatch
resp = chosen_handler.process_request(req)
line 175, in process_request
line 523, in _process_newticket_request
self._do_create(req, ticket, action)
line 1382, in _do_create
line 293, in insert
line 20, in ticket_created
File "/usr/lib/python2.7/subprocess.py", line 172, in call
return Popen(*popenargs, **kwargs).wait()
File "/usr/lib/python2.7/subprocess.py", line 394, in __init__
File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
OSError: [Errno 2] No such file or directory
Guessing this is related to the hosting provider move?