Change Log

Below is a complete listing of changes for each revision of HighLine.

3.1.1 / 2024-08-18

3.1.0 / 2024-07-15

3.0.1 / 2024-01-20

3.0.0 / 2024-01-05

2.1.0 / 2022-12-31

2.0.3 / 2019-10-11

2.0.2 / 2019-04-08

2.0.1 / 2019-01-23

2.0.0 / 2018-06-10

2.0.0-develop.16 / 2018-05-12

2.0.0-develop.15 / 2017-12-28

2.0.0-develop.14 / 2017-11-21

2.0.0-develop.13 / 2017-11-05

2.0.0-develop.12 / 2017-10-19

2.0.0-develop.11 / 2017-09-25

2.0.0-develop.10 / 2017-06-29

2.0.0-develop.9 / 2017-06-24

2.0.0-develop.8 / 2016-06-03

2.0.0-develop.7 / 2016-05-31

2.0.0-develop.6 / 2016-02-01

2.0.0-develop.5 / 2015-12-27

2.0.0-develop.4 / 2015-12-14

This versions makes the code documentation 100% ‘A’ grade on inch. We have used inch and inch-ci.org to guide the priorities on documentation production.

The grade ‘A’ (on inch) number of objects on master branch was 44,22% (153/346). After this PR we have a 100% grade ‘A’ (344 objects).

There’s already a inch-ci.org badge on README.md. And now it’s all green!

We also bring some improvement on CodeClimate scores.

CHANGES SUMMARY

2.0.0-develop.3 / 2015-10-28

This version brings some improvements on documentation (switch to Yardoc). This is the first 2.0.0-develop.x version to be release as gem.

2.0.0-develop.2 / 2015-09-09

(by Abinoam P. Marques Jr. - @abinoam)

NOTES

This version brings greater compatibility with JRuby and Windows. But we still have a lot of small issues in both platforms. We were able to unify/converge all approaches into using io/console, so we could delete old code that relied solely on stty, termios, java api and windows apis (DL and Fiddle).

Another improvement is the beginning of what I called “acceptance tests”. If you type rake acceptance you’ll be guided through some tests where you have to input some thing and see if everything work as expected. This makes easier to catch bugs that otherwise would be over-sighted.

CHANGES SUMMARY

2.0.0-develop.1 / 2015-06-11

This is the first development version of the 2.0.0 series. It’s the begining of a refactoring phase on HighLine development cycle.

SOME HISTORY

In 2014 I emailed James Edward Gray II (@JEG2) about HighLine. One of his ideas was to completely refactor the library so that it could be easier to reuse and improve it. I’ve began my contributions to HighLine trying to fix some of the open issues at that time so that we could “freeze” a stable version of HighLine that people could rely on. Then I’ve began to study HighLine source code with James’ help and started to refactor some parts of the code. Abinoam P. Marques Jr. (@abinoam)

NOTES

CHANGES SUMMARY

METRICS SUMMARY

Some of the metrics used to track progress are summarized bellow. Some of them have got a lot better as Flay, Flog and Reek, others like Cane haven’t (probably because we didn’t commented out the new code yet)

CODECLIMATE

CANE - reports code quality threshold violations (lower is better)

FLAY - analyzes ruby code for structural similarities (code duplication - lower is better)

FLOG - measures code complexity (lower is better)

REEK - detects common code smells in ruby code (lower is better)

1.7.3 / 2015-06-29

1.7.2 / 2015-04-19

Bug fixes

1.7.1 / 2015-02-24

Enhancements

Bug fixes

1.7.0 / 2015-02-18

Bug fixes

Enhancements

1.6.21

1.6.20

1.6.19

1.6.18

1.6.17

1.6.16

1.6.15

1.6.14

1.6.13

1.6.12

1.6.11

1.6.10

1.6.9

1.6.8

1.6.7

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.5.2

1.5.1

1.5.0

1.4.0

1.2.9

1.2.8

1.2.7

1.2.6

Patch by Jeremy Hinegardner:

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.0.4

1.0.2

1.0.1

1.0.0

0.6.1

0.6.0

0.5.0

0.4.0

0.3.0

0.2.0 / 2005-04-29

0.1.0