Actions
action #65076
closed[process] rethink our project management tool decisions
Start date:
2020-03-31
Due date:
% Done:
0%
Estimated time:
Description
Motivation¶
In their retrospective meeting on 2020-03-31 the SUSE QA tools brought up the discussion point if we could use more github and less redmine (progress.o.o) .
Collected points¶
- Should we replace redmine with github?
- good about keeping separated: We still keep some independance of github; we keep "backlog" separated from "hot stuff"; no need to invest in migration
- good points about github: All in one place; more
- challenges: many other teams use progress and we would need to track progress tickets anyway (at least unless they move somewhere else as well)
- if we want to migrate: Two alternative approaches come to mind: 1. Move gradually be enabling issue tracking again on https://github.com/os-autoinst or https://github.com/os-autoinst/openQA and fade out progress, 2. Do a hard-cut transition by importing all open or all tickets from progress to github
Updated by okurz about 2 years ago
- Tags set to process, redmine, github
- Subject changed from rethink our project management tool decisions to [process] rethink our project management tool decisions
Updated by okurz about 2 years ago
- Status changed from New to Resolved
- Assignee set to okurz
I think nobody complained in the past two years. We have the github issue trackers enabled on our github projects so people can report issues there and we take a look same as we do for pull requests. So I guess that is working out as well.
Updated by okurz about 2 years ago
- Related to action #69316: Benefit from automatic issue updates on GitHub added
Actions