Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide what to do with the legacy setuptools tracker on bugs.python.org #174

Closed
ghost opened this issue Mar 24, 2014 · 2 comments
Closed
Labels
major Needs Triage Issues that need to be evaluated for severity and status. task

Comments

@ghost
Copy link

ghost commented Mar 24, 2014

Originally reported by: ncoghlan (Bitbucket: ncoghlan, GitHub: ncoghlan)


MvL pointed out that http://bugs.python.org/setuptools/ is currently still live and needs to be dealt with so people don't get confused about where to report setuptools issues.

@pje pointed out that there is some info on issues there that hasn't yet been replicated in the docs or migrated to this issue tracker, so it likely needs to be reviewed before the instance can be terminated.

MvL suggested making it read-only for the time being. That sounds like a good idea to me, but a better long term resolution is needed.


@ghost
Copy link
Author

ghost commented Mar 24, 2014

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):


I see several substeps.

  1. Disallow creation of new issues on the setuptools tracker. This might be as simple as setting roundup roles.
  2. There is already a header on each individual issue page, but not on the index page as linked above. If possible, adding a link to the index page would be helpful.
  3. The remaining 58 issues should be addressed - either transferred to bitbucket or closed as wontfix.
  4. Disallow commenting (essentially make the site read-only).

I would like to keep the tracker around for posterity, rather than terminating it. What is the cost of continuing to host the site for reference?

@ghost ghost added major task labels Mar 29, 2016
@pganssle pganssle added the Needs Triage Issues that need to be evaluated for severity and status. label Oct 19, 2018
@abravalheri
Copy link
Contributor

It seems that the old bug tracker was disabled and is no longer accessible from the old URL... so time might have solved this issue for us...

I think we can close this issue now, considering that the entire community is already used to the new GitHub system, but if anyone would like to keep it open please feel free to comment here...

jaraco added a commit that referenced this issue Feb 4, 2023
--HG--
branch : Setuptools-Distribute merge
extra : source : 28eb706c219004e2dd83dcd1db37d952e8c66908
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major Needs Triage Issues that need to be evaluated for severity and status. task
Projects
None yet
Development

No branches or pull requests

2 participants