Subject: CVS commit: pkgsrc/devel/ruby-jirametrics
From: Amitai Schleier
Date: 2024-10-27 20:47:58
Message id: 20241027194758.3DA6EFC7E@cvs.NetBSD.org

Log Message:
ruby-jirametrics: update to 2.7. Changes:

- Fixed misleading usage information when running jirametrics with
  no options.
- Fixed deprecated warning that would display if an unknown option was
  given to jirametrics
- Added info command from terminal for debugging purposes. If you are
  trying to figure out why the tool has calculated something in one way
  then this will dump out information about that particular issue that
  might be helpful. Usage jirametrics info ABC-123 where ABC-123 is the
  issue you want information on.
- Experimental: Trying out a way to visualize flow efficiency. I'm not
  convinced this is the right way yet but I'm making it public so I can
  get feedback. This may change. Add flow_efficiency_scatterplot to your
  configuration. If you want to try this from standard_project then
  specify the option show_experimental_charts: true.
- Fix: discard_changes_before was always intended to work either as an
  option under project or under html_report but there were cases where
  it was broken in the former case.
- Fix: There are legitimate cases where the calculated start and end
  times for an issue are exactly the same. Consider
  in_or_right_of_column where Done is legitimately to the right of that.
  In this case, we now pretend that the issue never started, which in
  almost every case will be the expected result anyway. In the cases
  where that isn't true, our configuration is probably wrong anyway.
- Deprecated: CycletimeConfig.started_time(Issue) and
  CycletimeConfig.stopped_time(Issue), which are now replaced with a
  single method that returns both:
  CycletimeConfig.started_stopped_times(Issue). This was necessary to
  fix the bug above, where started and stopped are the same.
- Added another quality check. It now checks for subtasks that aren't
  closed when the main issue is closed. This likely indicates that the
  issue is still in progress, despite what the status says.

Files:
RevisionActionfile
1.6modifypkgsrc/devel/ruby-jirametrics/Makefile
1.4modifypkgsrc/devel/ruby-jirametrics/PLIST
1.6modifypkgsrc/devel/ruby-jirametrics/distinfo