On Tue, Feb 25, 2020 at 04:23:58PM +0000, Thiede, Christoph wrote:
> Great to hear this!
> 
> 
> > Please give them a try and report any issues here on the mailing list.
> 
> Is it necessary that the fresh image has a changeset that includes loads of reorganizations? Furthermore, we have two empty changesets: [cid:cbfface1-11d1-4d18-a23b-b01b162ea453]
> 

Good catch. Here is what I see:

The change set named 'The root project' is associated with the root
MVC project, which is installed to provide an emergency evaluator
environment for error conditions that cannot be handled in Morphic,
but that might be handled in some other UI (MVC). The change set is
empty, which is good. Nothing should be changed here.

Change set 'Unnamed1' is associated with the home project, which is
the Morphic project that is open when you first start the image. It
might be better if the home project change set to be named 'The home
project' rather than 'Unnamed1'. And it would be good if this change
set was empty when the release image is first opened (unless the user
has decided to install Git tools, etc, during the image configuration).

The third change set is called 'Autogenerated-unload' and is empty.
I don't know where this change set came from, but it does not need
to be in the release image.

This should not be a concern for the 5.3 release, but I put
ReleaseBuilder-dtl.206 in the inbox to hopefully clean it up
properly.

Dave