We strongly recommend that you evaluate YouTrack 'Harmony' EAP builds in a test environment, since you will not be able to revert to YouTrack 5.x other than by rolling back to a pre-upgrade backup of your database and losing your progress along the way!
Please upgrade your environment to Java 1.7 before running YouTrack 6.0 EAP. Starting frombuild #11415,earlier Java versions are not supported.
With this EAP we introduce a new approach to evaluation of new features in EAP builds. By default, visibility (hence, availability) of new features in EAP builds are controlled by so called 'Feature Flags'. That is, you can enable and disable these features at your will.
Enabling New Features in Stand-Alone Builds
Basically, a feature-flag is a JVM '-D' start parameter that you must provide when you start your YouTrack Standalone EAP Build. You can provide these parameters either in the starting command (thus features will be enabled for the current session only) or in the configuration file of your JVM (thus you don't need to control constantly whether you have enabled the feature or not).
Feature-flags are divided in two types:
General. These feature-flags are binary, and allow only switching a feature on/off for your YouTrack Standalone server. That is, when such 'general' feature in enabled, it is available for all users on your server ('All Users' group).
Per User Group. These feature flags allow enabling features for both all users and specific user groups only. To enable a feature with such flag, you can use two methods: binary 'true' value and with a list of user groups, to which the feature should be available. For example:
Read more about YouTrack Java Start Parameters >
Currently Available Feature-Flags
If a parameter supports customizing user groups, then you should provide a comma-separated list of groups.
Java Start Parameter
Custom User Groups
New 'Geeky' UI
New Reports Screen
Canvas Image Tool
Customizable Keyboard Shortcuts
Dashboard with Widgets
UI Redesign:FSI & create/edit issue mode
The new 'AND' operator in search queries is enabled, by default, and is not controlled by any feature-flag.
In any other regard, installation/running procedures are similar to those of the released builds.