view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

0.244   2021-07-23  Released-By: PERLANCAR; Urgency: high

        - Merge release 0.243 and 0.243.1.


0.243.1 2021-07-23  Released-By: PERLANCAR; Urgency: medium

	- [cli format-bencher-result] Add option --as to allow formatting
	  as Benchmark.pm result.

        - UPDATE: rename release from 0.243 to 0.243.1 due to conflict.


0.243   2021-01-20  Released-By: PERLANCAR; Urgency: medium

	- Add CLI: gen-bencher-scenario-from-cpanmodules.


0.242   2019-08-08  Released-By: PERLANCAR; Urgency: high

	- No functional changes.

	- Adjust to renamed dep: Data::Clean::JSON -> Data::Clean::ForJSON.


0.241   2018-04-03  Released-By: PERLANCAR

	- bencher-module-startup-overhead: Allow imports.


0.240   2018-02-18  Released-By: PERLANCAR

	- Add utility: bencher-for.

Changes  view on Meta::CPAN

	- Normalize Module/SubModule into Module::SubModule.


0.03    2016-01-08  Released-By: PERLANCAR

	- Rename module/dist from App-BencherAll to App-BencherUtils.

        - Add script: list-bencher-results.

	- [Incompatible change] option 'log_dir' is now renamed to
          'results_dir'.

	- Add option --precision-limit (passed to bencher).

	- [Bugfix] Reorder: we now bench first to let all the hooks
	  properly executed the first time.

	- [ux] bencher-all*: Add completion for --include & --exclude.

LICENSE  view on Meta::CPAN

changed that file, and provided that you do at least ONE of the following:

  a) place your modifications in the Public Domain or otherwise make them
     Freely Available, such as by posting said modifications to Usenet or an
     equivalent medium, or placing the modifications on a major archive site
     such as ftp.uu.net, or by allowing the Copyright Holder to include your
     modifications in the Standard Version of the Package.

  b) use the modified Package only within your corporation or organization.

  c) rename any non-standard executables so the names do not conflict with
     standard executables, which must also be provided, and provide a separate
     manual page for each non-standard executable that clearly documents how it
     differs from the Standard Version.

  d) make other distribution arrangements with the Copyright Holder.

4. You may distribute the programs of this Package in object code or executable
form, provided that you do at least ONE of the following:

  a) distribute a Standard Version of the executables and library files,