Commit 20a22bad authored by Leo Gordon's avatar Leo Gordon
Browse files

New changes for version/2.2

parent 329cc26a
Version 2.2 - 'analyses_pattern'
* Running and maintenance of pipeline subsets has been made easy with -analyses_pattern option in
that understands ranges and additive/subtractive merging. You can refer to analyses in many different ways.
-analyses_pattern 1..9 # show scheduling for a range of analysis_ids
-analyses_pattern 1..9,11..15 -run # run a scheduling iteration for two ranges of analysis_ids
-analyses_pattern fasta% -sync # sync analyses matching a pattern
-analyses_pattern 1..9-5-report -loop # loop over a range except two analyses
-analyses_pattern 1..9,fasta% -reset_all_jobs # reset all jobs belonging to a range and a pattern
-analyses_pattern foo,bar,baz -reset_failed_jobs # reset failed jobs belonging to three analyses by names
* The same option is available in to constrain the set of analyses to specialize into (fully works with -can_respecialize 1 mode)
* Detailed log of Scheduler's decision-making process is available
* and runnable have been reworked and are now better adapted for quoted arguments
* Doxygen API documentation packaged with the code
* Scripts' man pages converted into HTML and packaged with the code
* New docs about installing eHive, running eHive and running MPI jobs with eHive
* Using rawgit to render HTML docs hosted on GitHub (impossible otherwise)
* No schema changes since version/2.1 : the same database should continue to work with newer code without patching
Version 2.1 - 'multirole'
......@@ -6,11 +6,16 @@ Checklist to release a new eHive version
2. Update the Changelog manually using a text editor
3. Review, install.html and running_eHive_pipelines.html, change the version number in (for rawgit)
3. Review, install.html and running_eHive_pipelines.html,
change the version number in for the future version (for rawgit)
4. Regenerate docs/hive_schema.html, docs/scripts and docs/doxygen by running
5. Regenerate docs/scripts/index.html if you have 'tree' installed
6. After branching make sure master will have a new Bio::EnsEMBL::Hive::Version .
6. Check all of the above into master
7. Create a new version/x.y branch
8. After branching make sure *master* will have a new Bio::EnsEMBL::Hive::Version .
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment