Well!

We already have two slots taken!

One is:

Static Analysis for ObjectScript with  CacheQuality 

It's a CI compatible static analysis to for ObjectScript codebase which finds bugs and obeys code guidlines using a set of managed rules from LiteSolutions (which is now better will sound as IRISQuality, @Daniel Tamajon? ;)

Another slot is a secret topic, will be announced just before the GS.

So we have two more, book your session on InterSystems IRIS Flash Talks from Developer Community!

Hi, Lassi!

Consider you have two databases on your production system:

AppData - with application data

AppCode - with the code for your solution.

AppData namespace maps classes needed for the application in AppCode.

You deploy your releases only in AppCode namespace. In this case, you either delete everything before deploying the latest release or delete and create a new AppCode database the with latest release.

And you shouldn't bother of deleted classes in the repo ;)

Great article, Eduard, thanks!

It's not clear though what do I need to have on a production host initially? In my understanding, installed docker and container with IRIS and container with IRIS is enough. In that case how Durable %SYS and Application data (USER NAMESPACE) appear on the production host for the first time? 

Hi, Alessandro!

Thanks for the great post!

I wonder if Cube Relationships can address the same problem? e.g. if we have in this case two cubes: Patients and Doctors based on DeepSee.Study.Patient and DeepSee.Study.Doctor respectfully would basic synchronization of the cubes solve all the update issues?

If you can provide me access to an IRIS system on GCP Cloud, then sure.

You can provide the access to IRIS on GCP by yourself - it's open for everyone, as listed in the announcement.

What functionality would you like to see, and what would the target audience be?

This is simple. I wonder, what are the benefits of QEWD for developers on IRIS.

Note: I'm not around to do anything until early September

No rush here.

Hi, Ernesto! This is great!

You can make a Pull Request to the repo - so everyone can review/comment the changes too

Speaking about IRIS export - yes, it exports with <Export generator="IRIS"> which makes it complicated to import into Caché and Ensemble without manually changing the file.

I'd suggest @Kurro Lopez to export releases for IRIS and Caché/Ensemble separately for now and invite @Stefan Wittmann and @Benjamin De Boe to share guidelines what is the best way to develop on IRIS and make it available for Caché/Ensemble too.