Lei Zhang (Harry)

Also, definition objects should be extensible, i.e. there could be a section of extended parameters for platform builders to extend the functionality of TraitDefinition etc.

@kminder @dhiguero Just updated the spec description based on your inputs, they are valuable! We will leave some features as Non-Goal for this release, for example: 1. Make `.schematic` fully...

> Speaking of consistency, what about using `kind` for all. > > ```yaml > apiVersion: core.oam.dev/v1alpha2 > kind: Application > metadata: > name: application-sample > spec: > components: > -...

Thanks @Haishi2016 , it seems interesting! Note with ##336 addressed, we should be able to use `ApplicationConfiguration` to model such Deployment for component level. Also, for: > ... we have...

@Haishi2016 yeah that's the current idea in my mind. Would you like to work on #336 to design how we can model revision in detail? We can work together to...

@draveness ApplicationConfiguration is indeed the configuration for the app. Essentially: 1. Your Application is composed by a bunch of Components, ref: https://github.com/oam-dev/spec/issues/334 2. ApplicationConfiguration = Apply operational capabilities to your...

Add this in milestone which is closely related to application level rollout and revisioning.

So the workflow is: 1. User create [`Application`](https://github.com/oam-dev/spec/issues/306) object named `my-app`. 2. OAM runtime generate application revision named with `-v1` suffix. 3. User create `Deployment` object named `my-deploy`, reference `my-app`...

@erdun Yes! I think you are talking about a Traits Registry, correct? /cc @wonderflow @ryanzhang-oss

A related issue would be "global trait".