Konrad Kleine

> @kwk > A new migration/update is performed when the spacetemplate is updated. This means that a new pod was spawned and doesn't have the old cache state. > If...

> Looks good to me. Are you working on the item mentioned in the description? Also how about changing other places where version is used? @baijum I have worked on...

> What is the story/task reference for this PR? There is none. This is cleanup work and stabilization work. Do we have an issue for this already? I don't want...

> This contains the state to metastate mapping action rule and the necessary changes to the existing templates. @michaelkleinhenz can you please explain in more details what this does and...

@jarifibrahim good points. But can you elaborate how a hash makes things easier? Shouldn't we really start using push notification through web sockets to update clients? That should solve the...

> It's fine if two users try to update the description and only the latest one is saved. @jarifibrahim how is that fine at all? I have encountered the situation...

This PR presents an idea to deal with Versioning more easily, less error-prone and centralized: https://github.com/fabric8-services/fabric8-wit/pull/2263

I can understand what you want but `parent.id` irritates me. What is `parent.name` for example? That doesn't exist.

@sanbornsen yes, we can do this and it will be handled similar to type groups internally because the way n:m relationships are handled there.

> If I add {'parent.id': { '$EQ': '00000-0000-0000-000000'}} or {'parent.number': { '$EQ': '132'}} then the query should give me all the child items of these items. @sanbornsen it makes a...