Who rated this post

Just a thought, guys.

I'm sure I mentioned about stability before and suggested to Checkpoint that it does not matter how secure a product is 'marketed' for, if the service suffers stability issues, the overall Checkpoint experience will be tarnished.

I would personally like to see a supported mature and feature train release. 
Example:
R82 - Feature release
R81.20 - Recommended Release
R81.10 - mature release (Support for 3 years, once version is deemed mature)

The positives of this:
Clients investment is protected while maintaining stability for the features they are using.
Certification investment could potentially be longer if you are certified against recommended, which last until mature train is expired.