- This topic has 4 replies, 2 voices, and was last updated 6 years, 1 month ago by
.
- Posts
We have decided to switch to the tracker at Github for issue organization and bug reports. It is the better tracker system. And our issue tracker at the page is in the way for the port of the page to Drupal 8. The issue tracker module is not ported yet. And most probably never will.
New issues goes already into the Github tracker. The remaining issues at our issue tracker will be dealt with as far as possible. And the rest will be ported to the Github tracker then. New bug reports and issues should be started at the tracker at Github if possible.
We will have a grace period until the next Bforartists release is ready, which is expected to be two or three months away. The current Bforartists version still links to our issue tracker for bug reports. So we cannot close it immediately. After the new version is out, and the report a bug link in the Bforartists goes to the Github tracker, we will start the port of the webpage. And then the tracker with all its content will be gone.
– Reiner
Seems that we have to move a bit faster than expected. The spambots are making it through again. This time at the tracker …
Done. The tracker is now not longer publically available. Please use the tracker at Github: https://github.com/Bforartists/Bforartists/issues
I noticed the “report a bug” link on top of the menu directs to Github now. – The problem I see with this is that a new account is needed to post there. I know from myself, that I constantly click away from something like this. In fact I was still too lazy to make an account there. – In order not to miss any bug reports from “non developer” users, it would be better to link the “report a bug” menu item to a dedicated section here in the forum. – It´s up to the developers then to put it into Github afterwards, but that should make it more organized in the tracker anyway I believe?
Yes it’s a second account, and yes i know, it’s a hurdle. But the Tracker remains the best place to report bugs. We have already now ways too much organization work to do that could be better spent in actual development. When we start to have two places, and need to port all reported bugs over to the tracker, then this slows us even more down.
So please be so kind and make a Github account when you want to report a bug
- You must be logged in to reply to this topic.