Hi, Steve!

Thanks for your feedback! 

Does it have to be a Github repo or can I use BitBucket ?

It can be any public repository: Github, BitBucket or Gitlab. But today we have the embedded support only for Github. E.g. if you submit Github repo in the application OE will use README.md as description, LICENSE.md as license and we plan to introduce more support in the near future.

You can add the request for BitBucket support in Open Exchange issues.

Also - if we find an error  (eg WebTerminal on IRIS), can we leave a comment generally or for the developer ?

Every application has either repo with issues or the support link which are intended to receive feedback, bug reports, and feature requests.

If you find an error on Open Exchange, please submit it here! )

Hi, Stefan!

In this situation, I would suggest using RELEASES approach for different InterSystems Data Platforms. E.g. you can generate XML release package from the code base in git and then replace all the specific places for a given version on a build release phase. As a result you will have different XML packages for Ensemble and for InterSystems IRIS and have one code base, say in IRIS.

For example, you can see that approach @Eduard Lebedyuk used for RESTForms distribution. There are 2016.1 and 2016.2 release packages which can be installed in 2016.1 and 2016.2+ Caché or Ensemble versions respectfully.

To simplify release building I can recommend ISC.DEV utility which can export a release or patch file(upon git commits) for a given mask of classes.

HTH