Hi peeps!
That’s more Q & As added the original post. Keep asking questions as it helps others in the community have a clearer picture of what to expect in the coming months!
Just to follow up on a few other points.
@christianknoll
For the charts we have on the roadmap to support filters and the full record set (unfiltered). The Alpha Preview II did not include both.
@cherub-chum
Thanks for the suggestion. We are currently using CDK tables following a reactive design with the data provided separately via API. Noted the loader does appear to look like loading the full page, but in fact it is loading only data – something we have raised with the development team to resolve in the future sprints.
Regards to the PDF library, as part of this whole exercise and development is reviewing the current libraries we have and identifying how and what needs to be upgraded, dropped or added. I’ve noted down the word doc generation.
@Watt_Wing
It always comes down to the phrase “it often depends”. In a SuiteCRM project I would recommend making a call based on how heavily customised is the system. Are there alot of the front end customisations i.e. javascript injections, new radical views etc. If they are, then since SuiteCRM 8 will be focusing on that then potentially it would be best to wait at least to see how much needs to be adapted (from a beta or release candidate release) . You will also have to potentially consider the learning curve of a new language to best utilise the new framework so in my suggestion would be that you work with what you have, whether this is SuiteCRM 7, and trickle into your future schedule POCs on the newer framework and review at certain milestones i.e. pre-production release, launch, and post launch.
Regards to the backend customisations those customisations will be more likely take minimal effort to upgrade so that would be another win to just get started on SuiteCRM 7 and easily transfer over when your team are ready to SuiteCRM 8 based on the review points of the project.
Of course we will always be here to help our users to migrate, as said earlier, with as much direct input as possible 
@christianknoll
Of course there are many tasks ahead, but we are loving the challenge. Since we are open source and thus collaborative there may be smaller delays but these delays are to be expected as they represent the review and influence that our community has on the software development cycle. If we didn’t take on board our members comments, then we would just be source available not open source.
Thanks again everyone for your comments and interaction on this thread. 