pdt
pdt copied to clipboard
eclipse-pdt
(Most) TICKETS ARE MISSING FROM THIS TRACKER (GitHub), documentation suggests otherwise
Describe the bug The PDT project tracked its issues on bugs.eclipse.org like other Eclipse sub-projects until recently. This tracker on GitHub was only created a few months ago. Moreover, tickets on bugs.eclipse.org were visibly never transferred here. As a result, that vast majority of reported issues in PDT cannot be found on this tracker.
Unfortunately, the README.md and CONTRIBUTING.md files imply otherwise:
Search for issues: https://github.com/eclipse/pdt/issues Create a new report: https://github.com/eclipse/pdt/issues/new
Additional context Tickets on bugs.eclipse.org are no longer in the PDT product, but rather in the PDT component of the "z_Archived" pseudo-product.
This was migration cons. Anyway in old tracker was incredible mess and none really care since years :/ In near feature eclipse bugzilla will be replaced by foundation gitlab instance.
What you suggest? Link for old tracker somewhere in README or CONTRIBUTING or WIKI?
Thank you Dawid, I admit I do not know very well how well triaged the PDT product's issues was. Are you sure that Eclipse's Bugzilla will be replaced by a GitLab instance? And if so, would that solve or help with this issue?
That would seem to be the intention during 1H2022 for projects still tied to the infrastructure that exists at eclipse.org, according to https://gitlab.com/gitlab-org/gitlab/-/issues/195865 .
Thank you very much @nitind though I see nothing about 1H2022 there.
I am skeptical about that request, but at this time, it does not contain anything concrete which would solve or help with this issue, and even if it was realized in the proposed timeline, it could take 2 years to complete that replacement.
I will try to get more information about the foundation's plans, but in the meantime, one possibility would be to go back to bugs.eclipse.org and attempt a new migration when a migration path is created. Otherwise, indeed, all references to tracker(s) should point to both. I had already updated the wiki (as much as I could - it was non-trivial), so README and CONTRIBUTING would be left.