Thanks for this work. to moving to GitHub (or GitLab). It may be worth considering whether any more effort should be put in Mantis at all – except possibly to migrate content to GitHub (there are some scripts available which could be modified). Leaving the tracker frozen like the old Kitware trackers would also be fine. There is relatively minimal recent activity on the current tracker because of the reliability and email issues, lack of OAuth, etc., though the history is useful to keep.
GitHub’s issue tracker is still very basic, but it should be good enough to manage Slicer issues. When source code hosting will transition to GitHub then we’ll have to use GitHub’s issue tracker anyway (for managing pull requests, etc), so it would be simpler if we don’t need to manage two trackers. It’ll be also great to have integration with source code repository and not requiring separate account.
I think the simplest would be to prevent adding new issues to Mantis, but we should be able to update/close issues. When we closed or migrated all issues, we can make the repository read-only.
Actually, the tracker is available. The source integration plugin has a nasty feature whereby it blocks (queues) all requests by the same client behind the long-running “import” – making it appear that the server is hung. Meanwhile, any other client can access the tracker and the load is miniscule.
@jcfr kill the import and/or use incognito mode and/or another browser. I can assure you that the server is fine.
Bumping this thread since there’s already been some good conversation on this topic.
I have found it pretty difficult to use the search within the Mantis Tracker to find relevant results. It’s hard to quickly find if there is already an issue for a bug that I observe.
ITK recently moved from their issue tracker (JIRA) to GitHub issues. See this post on their forum. Here is another post they had about using GitHub labels. For the most part I think Github Issues, Labels, and Milestones could replace a lot of primary functionality in the issue tracker. There isn’t default assigning of issues, but maybe some github apps could supplement any missing features.
Also Github has issue templates which could encourage detailed steps to reproduce, platform, expected behavior, etc. which would be similar to the header fields on the Mantis Tracker. ITK is also using github issue templates to encourage users to provide details about bugs/features/etc. See ITK Issue Template.
Since mantis stores issues in a structured way (not just somewhat encouraging structure by offering a template), I find it much more efficient to locate issues in Mantis compared to GitHub.
However, I agree that probably GitHub’s issue tracker would be sufficient for Slicer, and definitely more accessible to users and developers, because most people are already familiar with GitHub, they don’t need to register yet another account, and the issue tracker integrates well with other GitHub features.
I think we should just first release Slicer-4.10.1, then move Slicer’s official repository to GitHub (still SVN is the official repository) and then switch to GitHub’s issue tracker.
It would be nice to switch to github repository and issue tracker at the same time, to be able to leverage all the benefits of integration between github tools. However, there is no strict dependency, so we could start using github’s issue tracker for new issues any time.
@jcfr what is the planned date for switching to git?
(Jean Christophe Fillion Robin (Kitware))
This is the next major Slicer task on my list, we should expect the transition to happen in the next few weeks.
Yesterday, I tried to register to the bug tracking system without success, I didn’t get back an email that probably should have contained my password. Following the advice of @lassoan, I will post some issues I encountered in this thread.
I tried the issue with the ruler not being visible after loading a scene also with the nighlty build from 2019-08-29. It was the same there. Regarding the other two issues, the cited source code is unchanged to version 4.10.2 and I debugged those issues, so I assume they are still relevant.
So far no email received.
Please remove my email address from your previous post - thanks!