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
Interestingly enough, it does not look like this has been explicitly discussed. Shall we make github issues the place to track bugs?
Previously we identified that file uploads were a major benefit for source forge that github issues was missing. Now with zenhub.io and file uploads for github as well, it does seem we have really hit parity between the two.
If there is no objection, I would then next like to discuss what should be done to really make this migration happen. For example, an update to the welcome message in the lobby would reach a number of people.
The text was updated successfully, but these errors were encountered:
I get the sense the answer is yes.. So the next question is, how do we get bugs out of sourceforge? Perhaps a better question would be if we should. Perhaps we can simply solve bugs in-place from that queue, and make sure new ones are tracked in github issues. Then eventually the SF queue should shrink to zero.
Interestingly enough, it does not look like this has been explicitly discussed. Shall we make github issues the place to track bugs?
Previously we identified that file uploads were a major benefit for source forge that github issues was missing. Now with zenhub.io and file uploads for github as well, it does seem we have really hit parity between the two.
If there is no objection, I would then next like to discuss what should be done to really make this migration happen. For example, an update to the welcome message in the lobby would reach a number of people.
The text was updated successfully, but these errors were encountered: