[teiid-designer-dev] [teiid-dev] VDB Versioning Feature

[Ramesh Reddy]

On Thu, 2010-02-18 at 15:43 -0500, Steven Hawkins wrote:
> At first glance in the scenario you list below, there's no need to
> even bother with the promotion concept.  You would just install the
> new version (with a new name) and let apps point over to it as they
> are ready.  
> 
> To achieve the flow your suggesting without versioning would actually
> require an extra step.  Prior to promoting the next version, you would
> need to deploy a duplicate of the current version with a new name.
> Then the small set of apps not ready for the update would need to have
> their connections pointed to the copy.  Then you could safely promote
> the next version without interrupting the lagging apps.

+1

Especially when in this situation clients have to anyhow modify their
client settings to explicit version number to avoid the automatic
promotion. Instead they need to change the name. 

Another side effect of with the version scheme is you have clients
deployment profiles segmented, some are banking on the "active-default"
behavior and some are banking on the explicit version behavior. Say once
everybody migrated to same "latest" version, it is good likely hood that
the client profiles with explicit version numbers will not be re-visited
to fix them to use "active-default" thus they fail to promote themselves
when next version rolls around.

Ramesh..