Moving trac (Bug reports & patches) to GitHub.

The projects speaking tube.
Add your two cents if you want to.
Post Reply
User avatar
vexed
Inactive
Inactive
Posts: 2538
Joined: 27 Jul 2010, 02:07

Moving trac (Bug reports & patches) to GitHub.

Post by vexed » 25 Mar 2019, 00:43

Because of the intermittent issues with our local bug tracker (trac), we have decided that we will no longer be using trac, and instead, have moved to Github.


Our new home for bug reporting & patches is available here: https://github.com/Warzone2100/warzone2100/issues

Sorry about the inconvenience.


Note, that we will migrate all trac tickets to github sometime in the future, for now, it is read only.
/facepalm ...Grinch stole Warzone🙈🙉🙊 contra principia negantem non est disputandum
Super busy, don't expect a timely reply back.

User avatar
alfred007
Regular
Regular
Posts: 563
Joined: 31 Jul 2016, 06:25
Location: Stuttgart, Germany

Re: Moving trac (Bug reports & patches) to GitHub.

Post by alfred007 » 30 Mar 2019, 01:57

Maybe you should also update the "Bug reporting" link at wz2100.net

User avatar
alfred007
Regular
Regular
Posts: 563
Joined: 31 Jul 2016, 06:25
Location: Stuttgart, Germany

Re: Moving trac (Bug reports & patches) to GitHub.

Post by alfred007 » 28 Jun 2019, 00:57

The link in the chapter "Reporting bugs" of readme.md is still leading to trac and should be updated.

Forgon
Code contributor
Code contributor
Posts: 276
Joined: 07 Dec 2016, 22:23

Re: Moving trac (Bug reports & patches) to GitHub.

Post by Forgon » 28 Jun 2019, 08:14

alfred007 wrote:
28 Jun 2019, 00:57
The link in the chapter "Reporting bugs" of readme.md is still leading to trac and should be updated.
This problem is addressed by PR #374.

Another problem is that Trac tickets are updated if commits contain
references to pull requests. For example, merging PR #382 into master
updated ticket #382 among others.
I appreciate that someone has probably worked on the problem recently
(I notice that PR references no longer lead to comments in Trac tickets)
but there are still annoying e-mail notifications in my mailbox that
suggest that something remains switched on that should be switched off.

User avatar
WZ2100ModsFAn
Trained
Trained
Posts: 344
Joined: 15 Apr 2018, 17:25
Location: United States.

Re: Moving trac (Bug reports & patches) to GitHub.

Post by WZ2100ModsFAn » 30 Jun 2019, 02:10

Probably cause the trac has never been updated in years.
Apologies if i dont see your post
central time usa

User avatar
CMDPete
New user
Posts: 4
Joined: 07 Jul 2019, 16:21

Re: Moving trac (Bug reports & patches) to GitHub.

Post by CMDPete » 07 Jul 2019, 16:37

Will you be moving over all the documentation from trac/wiki to GH?
There appears to be a lot of outdated documentation scattered throughout the site.

User avatar
WZ2100ModsFAn
Trained
Trained
Posts: 344
Joined: 15 Apr 2018, 17:25
Location: United States.

Re: Moving trac (Bug reports & patches) to GitHub.

Post by WZ2100ModsFAn » 09 Jul 2019, 00:21

CMDPete wrote:
07 Jul 2019, 16:37
Will you be moving over all the documentation from trac/wiki to GH?
There appears to be a lot of outdated documentation scattered throughout the site.
It's because the trac is broken.
The registration is down and so is the bug reporting. That's why they moved to github.
Also note it could take a long time to bring all of this to the github issues.
Like i said.
WZ2100ModsFAn wrote:
30 Jun 2019, 02:10
Probably cause the trac has never been updated in years.
Apologies if i dont see your post
central time usa

Post Reply