You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Original comment byjaraco (Bitbucket: jaraco, GitHub: jaraco):
I see several substeps.
Disallow creation of new issues on the setuptools tracker. This might be as simple as setting roundup roles.
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.
The remaining 58 issues should be addressed - either transferred to bitbucket or closed as wontfix.
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?
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...
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.
The text was updated successfully, but these errors were encountered: