metric_fu Google Group

[ANN] metric_fu 4.2.0 released

benja...@benjaminfleischer.com (Benjamin Fleischer) — Tue, 21 May 2013 03:21:38 UT

- Features
- Allow setting of the --continue flag with flog (Eric Wollesen)
*Fixes
- Allow the 2.0.x point releases (Benjamin Fleischer #75)
- Misc
- Make Location and AnalyzedProblems code more confident (Avdi Grimm)

Included a checksum<[link]>

[ANN] metric_fu 4.1.3 Released

bfleisc...@gmail.com (Benjamin Fleischer) — Mon, 13 May 2013 18:53:47 UT

A bugfix release of MetricFu

- Features
- Tests now pass in JRuby and Rubinius! (Benjamin Fleischer)
- Fixes
- Line numbers now display and link properly in annotated code
(Benjamin Fleischer)
- No longer remove historical metrics when testing metric_fu
- Churn metric handler won't crash when no source control found (Dan

MetricFu 4.1.1 released, bug fixes

benja...@benjaminfleischer.com (Benjamin Fleischer) — Wed, 17 Apr 2013 04:58:25 UT

See change log

[link]

Thanks to all contributors

I'm also working on compatibility with non-mri rubies, though I'm not sure
how valuable that is at this time.

-Benjamin

Re: [metric_fu] New release 3.0.0 is out

d...@mayerdan.com (Dan Mayer) — Mon, 11 Feb 2013 00:12:54 UT

Congrats on the release!

Dan Mayer
[link]
[link]

On Sun, Feb 10, 2013 at 10:25 AM, Tobias Pfeiffer <

Re: [metric_fu] New release 3.0.0 is out

tobias.pfeif...@student.hpi.uni-potsdam.de (Tobias Pfeiffer) — Sun, 10 Feb 2013 15:25:44 UT

Great work and thanks Benjamin, will check it out! :-)

New release 3.0.0 is out

bfleisc...@gmail.com (Benjamin Fleischer) — Sun, 10 Feb 2013 15:12:38 UT

3.0.0 is out

[link]

Features
* included metrics: churn, flay, flog, roodi, saikuro, reek, 'coverage', rails stats, rails_best_practices, hotspots
* works with ruby 1.9 syntax
* can either load external coverage metrics (rcov or simplecov) or run rcov directly

Re: [metric_fu] Prepping for a new release, 2.1.4.pre5

pnascime...@gmail.com (Pedro Nascimento) — Tue, 05 Feb 2013 00:35:45 UT

Just a minor advice: if we want to follow semantic versioning (which I
think we should), this should be versioned as 3.0, given it break some
functionality for ruby 1.8 users.

Pedro Nascimento

HE:labs
[link]

I still have a bit I'd like to do before releasing metric_fu, 2.1.4, but

Prepping for a new release, 2.1.4.pre5

bfleisc...@gmail.com (Benjamin Fleischer) — Mon, 04 Feb 2013 23:33:23 UT

I still have a bit I'd like to do before releasing metric_fu, 2.1.4, but
since 2.1.4.pre5 contains a lot of new functionality, I invite you to test
it out

New
* can run from the command line just like metrical (i.e. no need for
metrical)
* uses latest ruby_parser, works on ruby 1.9
* rails best practices is disabled in ruby 1.8

Re: metrical/metric_fu gives the error: uninitialized constant MetricFu::Configuration - how do I require this properly?

bfleisc...@gmail.com (Benjamin Fleischer) — Mon, 07 Jan 2013 22:54:11 UT

Hi NullVoxPopuli-
Which version of metric_fu are you using? If not using the latest, could
you please create an issue on [link]
and continue this conversation there?
I suspect you are using a version I released that had a bug in it. Try
updating your metric_fu gem to the latest version. Also note, for what

metrical/metric_fu gives the error: uninitialized constant MetricFu::Configuration - how do I require this properly?

lt.s...@gmail.com (NullVoxPopuli) — Mon, 07 Jan 2013 22:23:36 UT

Originally, I was following this guide: [link] But
that didn't work (got the same error as I'm getting now). and I read that
using metrical is supposedly easier, as it is supposed to do a lot of the
set up for you. But the following happens:
From the Terminal,
$ bundle exec rake spec

Re: [metric_fu] MetricFu, The Development Continues

d...@mayerdan.com (Dan Mayer) — Sat, 05 Jan 2013 23:10:58 UT

I worked on this back in my days with Devver, it can definitely be a bit
interesting to have all of that data to crunch over time. Right now
codeclimate is definitely the best version of that sort of tracking. Code
Climeate doesn't use metric_fu directly but utilizes many of the same
underlying tools as metric_fo.

Re: [metric_fu] MetricFu, The Development Continues

bfleisc...@gmail.com (Benjamin Fleischer) — Fri, 04 Jan 2013 22:48:00 UT

Replies below

This is currently being done by the codeclimate.com project (e.g. see
[link] ) and was done by the now
defunkt Caliper project (by devver folks).

You might want to take a look at e.g.
[link]

Re: [metric_fu] MetricFu, The Development Continues

r...@cfcl.com (Rich Morin) — Thu, 03 Jan 2013 23:11:36 UT

Congratulations or commiserations, as appropriate. Regardless, thanks!

For some time, I have been interested in the idea of running metric_fu
in some sort of "continuous harvesting" fashion. That is, download gems
and such, run metric-fu on them, and save the results in a database.

Could you answer a couple of questions about the current state of affairs,

Re: MetricFu, The Development Continues

jake.scru...@gmail.com (Jake Scruggs) — Thu, 03 Jan 2013 22:50:28 UT

Just chiming in to say thanks to Benjamin for taking over the managing of
this project from me. I'm still on the mailing list and may help out from
time to time but not to the degree I did before.
-Jake

MetricFu, The Development Continues

bfleisc...@gmail.com (Benjamin Fleischer) — Thu, 03 Jan 2013 22:06:22 UT

Hi all, I'm Benjamin Fleischer, the new 'Lead Developer' for metric_fu's continued development.

I created a new github organization 'metricfu' such that the project is now located at [link] . It is now the official metric_fu repo.

It contains patches that I've manually applied from the original jscruggs/metric_fu pull requests and issues, as well as subsequent work that I've done trying to improve 1.9 and 1.8 compatibility and well as some structural reorganization in an attempt to isolate dependencies and narrow the interfaces. I've also released an updated version of roodi and make fork and update some other dependencies. I'm also contacting some of the maintainers of the dependencies, e.g. churn, about updating their dependencies. This is just the beginning.