Using the GitHub issue tracker for 2.0
Posted: Sat Jul 20, 2013 6:04 pm
FYI: So far, we have used “local” ToDo lists for 2.0 development. As of today, we'll be using the GitHub issue tracker for this. Unfortunately, GitHub does not offer branch-based issue trackers, so we'll have to use labels to differentiate issues. Everyone please make sure to use the proper labels, at least the branch labels (2.0 and master).
We'll also use issue assignment, so if a label is assigned to a developer, consider it covered (which does not mean you shouldn't contribute to it). Also, if someone assigns a label to you, you can always “unassign” yourself if you don't have the time or don't think you're “right for this issue”.
YL
We'll also use issue assignment, so if a label is assigned to a developer, consider it covered (which does not mean you shouldn't contribute to it). Also, if someone assigns a label to you, you can always “unassign” yourself if you don't have the time or don't think you're “right for this issue”.
YL