Release HeuristicLab 3.3.13

[ascheibe]

Codename:

• Windischgarsten

New Features:

• Hive Statistics
• (?) Bin Packing
• (?) RoboCode
• (?) New Genetic Programming Example Problems
• (?) Additional accuracy metrics for classification models (and comparison to baseline algorithms)
• (?) ALPS
• (?) Breadcrumbs
• (?) Termination Criteria
• (?) Visualization
• (?) ONs

Release Steps:

Stable Branch:

1. Increment plugin and application versions
2. Update versions in plugin dependencies
3. Increment assembly file versions
4. Increment installer versions
5. Check and if necessary update year of copyrights
6. Check and if necessary update build configurations and project dependencies
7. Check if all unit tests are passed
8. Update samples
9. Create release tag
10. Merge commits back into trunk

Release tag:

1. Update target path in CustomPostBuildTemplate_UpdateLocalInstallation.cmd in project HeuristicLab-3.3
2. Build configuration Release Any CPU
3. Check if it compiles with mono
4. Remove unnecessary files from build output (*.vshost.exe, *.vshost.exe.config, *.vshost.exe.manifest, *.pdb, *.dll.config (do not remove DotNetScilab-1.0.dll.config, that's a plugin dependency), app.config)
5. Hide HeuristicLab 3.3.exe.config
6. Create zip file

Trac:

1. Attach zip file to Download wiki page
2. Update wiki pages Download, ChangeLog, ChangeLogPending, etc. (download button for current version is always called HL-Download.png)
3. Create new milestone for the next release
4. Change description of the current milestone into changelog style
5. Update ChangeLogPending to display tickets of the next release milestone
6. Complete current milestone and retarget all its remaining open tickets
7. Update default version in the trac Admin module

Documentation:

1. Update tutorial slides (latest version, number of plugins, algorithms and problems, features)

Marketing and PR:

1. Post info about new release on HEAL homepage, ​HeuristicLab Facebook fan page and LinkedIn
2. Write a release announcement for the Blog and send a mail to our mailing list
3. Update Wikipedia page
4. Push to github
5. Update Features page
6. Inform everybody else who might be interested

[gkronber]

r12793: set svn:ignore

[ascheibe]

r13093 made access service configuration file public