Updated QGISbugtracker (markdown)

Tim Sutton 2018-02-21 19:01:02 +02:00
parent 6e83375be0
commit 7ca557d2ed

@ -87,4 +87,6 @@ AGAINST:
- Some features are Enterprise-version only ( OpenCore model)
- **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Splintering of resources - we have many repos on GitHub - are we going to move them all? it makes the scope of the task huge.
- **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Breaking existing workflows - if we migrate fully to GitLab we need to migrate many other things - commit hooks, CI, all sorts of things people have set up based on the current locations of the source.
- **IMPORTANT AND IGNORED IN THE DISCUSSION SO FAR**: Breaking existing workflows - if we migrate fully to GitLab we need to migrate many other things - commit hooks, CI, all sorts of things people have set up based on the current locations of the source.
- have to come up with a plan to handle 'tagging'/tagging system of issues to be able to search tickets? I started with some idea in 2015: https://github.com/rduivenvoorde/temp/issues
- have to come up with a plan to either export (some) tickets from redmine OR decide to start with a clean (3.0) sheet??