Christie Warwick (Wilson)

Oh it already IS in the roadmap https://github.com/tektoncd/triggers/blob/master/roadmap.md /lifecycle frozen

> do we think that we have to keep the 1:N mapping so that TriggerWhatevers can spawn multiple PipelineRuns? @ImJasonH do you think it would be better to have 1:1?...

oooo i like that @siamaksade ! (also maybe: PipelineBlueprint?)

> hopefully this wouldn't involve a major breaking change if we did move to this, it would be a breaking change. im sure TriggerTemplates would continue to be supported for...

> so this isn't a proposal but more of a feature that is definitely happening? it's a proposal

> whenever I hear of a "recipe" i think of "wizardy" types of things which I avoid. The less coupling the better Totally: the less magic the better! And that's...

I think this is an important discussion to have before the beta release. talking with @dibyom last week i think he's planning to follow up on this. /remove-lifecycle stale

Drive by comment: via [TEP-0075](https://github.com/tektoncd/community/pull/479) we'll hopefully be adding support for richer result types (in this case objects with keys and values) so i wonder if it would be worth...

I've started this doc with my thoughts: [CI/CD and the development workflow](https://docs.google.com/document/d/1730VRKxKbvpR9LrmUHs6wjukvkiuL_CDidgf6zDJ7d0/edit#) - not sure the best medium to discuss this, but starting a doc seemed like a good starting...

I'd like to see this conversation through at some point but I think there's no sense of urgency (unless we start making decisions that preclude the possibility of supporting a...