2 comments

This behavior is expected when there is no active EAP. There are gaps between the EAP builds when there is no EAP for the next major version available and the previous EAP has already became a release.

0

your definition of 'expected' and mine are clearly very different.  i'd say it is enormously confusing.

0

Please sign in to leave a comment.