Trunk is now open as 7.2. Alpha2 should be released today, with Beta1 to follow on Oct. 13th. We'll end up punting most of the 7.2 work into 7.3, but if there is anything that seems high priority for the community, then its worth working in this window. 7.1.1 should only get critical fixes and doc updates from here out (with the exception of some additional JOPR work).
As we are nearing the end of 7.1.1, it's a good time to make sure we are on the same page with upcoming releases.
7.1.1 - Should be "CR" within a week or two. Only critical fixes and doc changes after that.
7.2 Will fork from 7.1.1 after it is in CR status. Since so much good work has been done in 7.1.1, it seems attractive to keep 7.2 on a relatively short time box, rather than the December time currently in JIRA. We would shoot for ~10/19 release (9 weeks from 7.1), which leaves only a short window for additional enhancements past the 7.1.1 work.
7.3 Would then be added as a new bucket and contain most of the work currently targeted at 7.2. Ideally 7.3 could be released before the holidays, but who knows what kind of availability everyone will have.
8.0 Remains further out, but the primary drivers should be AS 6.0 support, re-adding embedded mode, ensuring ease of use of all features independently of Designer (UDFs, views/procedures, etc.)
Currently when a preview VDB is deployed through Designer, the JOPR tool
connected to the same instance shows all these preview VDBs in its
Since we are consider preview vdbs as Design time stuff, should these be
hidden from the JOPR tool?
I personally do not like to see them, we can filter them for VDBS. The
same issue exists for data sources too. But we may not be able to filter
What is your opinion?