Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #27234

Closed (moved)
(moved)
Open
Created Aug 21, 2018 by Karsten Loesing@karsten

Clean up and gently refactor metrics codebases

This week seems like a good time to finally clean up and gently refactor the metrics codebases. There are currently no large, unmerged branches open, and we did not schedule any releases for this week.

I started making changes to all five codebases. Most of the changes are based on warnings produced by IntelliJ's Code Analysis tool. None of the changes are meant to change behavior.

Reviews will be a challenge, which is why I'm trying to do only one type of change per commit. Also, I'm pushing commits as early as I can while continuing to make more changes. I'd appreciate a 2-step review process where the first step is to very quickly decide whether a commit is useful or maybe even harmful and the second step is to review in detail whether changes in a commit are correct.

I'll post 5 branches as soon as I have a ticket number. I'll also comment whenever I post new commits to any of these branches.

Setting priority to high, because we should finish this work before resuming any other tasks.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking