Closed stefanseefeld closed 9 years ago
Changed the python group to have admin privileges. I'm checking if it's possible to "close" the Trac side.
On 02/07/15 02:12 PM, Rene Rivera wrote:
Changed the python group to have admin privileges. I'm checking if it's possible to "close" the Trac side.
Thanks !
Stefan
...ich hab' noch einen Koffer in Berlin...
Best I can do is delete the "Python" component in Trac. I would only be able to do that after you migrate all the issues. Since they will become unsearchable after I delete the component.
On 02/07/15 02:26 PM, Rene Rivera wrote:
Best I can do is delete the "Python" component in Trac. I would only be able to do that /after/ you migrate all the issues. Since they will become unsearchable after I delete the component.
Thanks for looking into that. I think it's best to keep things as they are right now, and instead advertise the github tracker for Boost.Python. I take it there are no hooks in trac that could be used to prevent new issue generation ?
I'm afraid that migrating issues isn't really feasible without losing information, so I think it would be best to close the issues of one at a time and just use the github tracker for new issues.
Stefan
...ich hab' noch einen Koffer in Berlin...
Hello,
I'm working on Boost.Python, trying to resolve a few of the open issues. I'd very much like to migrate existing issues from trac to the github tracker, as right now switching between the two, matching issues on trac with pull requests on github is quite painful. However, right now I'm unable to enable the issue tracker for the boost.python project as I lack admin rights. Would you please grant me these rights ? (Also, is it possible to close the boost.python trac instance ? (where by "close" I mean "prevent anyone from submitting new issues there") ?
Thanks, Stefan