<commit_before>.. _releases:

Release notes
=============

Disco 0.5.2 (TBD)
-----------------
New features
''''''''''''
- Ddfs can now distribute the blobs according to the amount of space available on the nodes.

- Disco now supports concurrent stages.  That means, a stage can start before
  all of the tasks of the previous stages have finished.  This option can be
  enabled for pipeline jobs.

- A Disco worker is available in `golang <http://github.com/discoproject/goworker>`.
  This worker only supports map-reduce jobs at the moment.

- The scheduler dictionary can now be sent as part of the job_dict in both the
  classic and the pipeline workers. The max_core option in this dictionary will
  limit the number of tasks from a job that can run.

Deprecated
''''''''''
- The deprecated merge_partitions option has been removed.

Disco 0.5.1 (April 16, 2014)
----------------------------
New features
''''''''''''
- Disco now uses folsom for monitoring purposes.  Folsom extracts some<commit_msg>doc: set the release date for 0.5.2.<commit_after>.. _releases:

Release notes
=============

Disco 0.5.2 (June 24, 2014)
-----------------
New features
''''''''''''
- Ddfs can now distribute the blobs according to the amount of space available on the nodes.

- Disco now supports concurrent stages.  That means, a stage can start before
  all of the tasks of the previous stages have finished.  This option can be
  enabled for pipeline jobs.

- A Disco worker is available in `golang <http://github.com/discoproject/goworker>`.
  This worker only supports map-reduce jobs at the moment.

- The scheduler dictionary can now be sent as part of the job_dict in both the
  classic and the pipeline workers. The max_core option in this dictionary will
  limit the number of tasks from a job that can run.

- By default, Disco is now installed in /usr instead of /usr/local.

Deprecated
''''''''''
- The deprecated merge_partitions option has been removed.

Disco 0.5.1 (April 16, 2014)
----------------------------
New features
''''''''''''
- Disco now uses folsom for monitoring purposes.  Folsom extracts some
{'fraction_non_alphanumeric': 0.13292336802270577, 'fraction_numerical': 0.015610217596972564, 'mean_word_length': 3.1633858267716537, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4691487', 'n_tokens_mistral': 619, 'n_tokens_neox': 578, 'n_words': 288}