-
Notifications
You must be signed in to change notification settings - Fork 143
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
Please deprecate bitbucket repository #2
Comments
Repo is deleted now, but it doesn’t look like all bug reports have been migrated :( |
Many of them were very old, it was unknown if they were still valid, and no one wanted to validate them as still being relevant. On the plus side, this does at least ensure that people won't mistake it for the right repo. |
Well, I have seen projects that do a last commit of REPOSITORY-HAS-MOVED.txt, and also projects that migrate issues automatically. We’ll have to report the bug with arguments named 'cls' ignored and write the test case again. |
(I just re-reported said issue, it's now #38 here) |
I'll admit I have zero time to work on this, if you have time to work on it, I'd be happy to give you commit access to fix the bugs. No one was fixing any of the bugs on bitbucket, no one is fixing the bugs here either, but a few more of them were fixed here than on bitbucket at least, which is why I dumped the old one. There's been a few people that submitted pull requests, when they have a test, I've been merging them when they look ok. But really, none of this alleviates the problem that Beaker needs someone to do releases and manage that, I rarely can find the time to do that. |
I've put out a tweet, and will also work at PyCon to try and find someone to act as an official maintainer. |
I understand your position; please accept my apologies if my tone was uncivil. |
https://bitbucket.org/bbangert/beaker/overview
still says "Beaker Official Mirror". There is no immediately obvious reference to the github repository there. I signed up and submitted a pull request months ago, only to realise now that the canonical source is here on github.
The text was updated successfully, but these errors were encountered: