Hi Ethan,
With regards to bug 7383. I see issues surrounding this bug as:
* Being able to ensure an AI client gets a manifest with keywords
which it supports (i.e. server running build Y, client running
build X, x<y)
* Being able to identify what build (of our bits) an AI client is
running
To achieve these two ends:
* The schema could define what changeset (of slim_source) the
feature being defined was added. (Perhaps just a changeset=###
attribute that can be added to features in the schema.) Then,
publish_manifest will store what the minimum changeset necessary
for that schema in the criteria database as a criteria.
* The client can send which changeset of slim_source it was built
off of in the AI server<->client criteria exchange.
* Then all that is necessary to ensure the client gets an
appropriate manifest is to have the AI webserver treat the
changeset criteria as just any other criteria -- no work
necessary.
I see this as requiring fairly little implementation (~5 days with
testing). Let me know what's might be missed by such an approach or how
else versioning could be done though.
Thank you,
Clay
