Javier Romero

Although I agree with this change, this may be considered a breaking change. I'd want to take a deeper look into the reasoning for the change, it's potential impact and...

@jkutner Can you update this PR with backward compatibility support? I would envision that we would warn about the misuse of the invalid namespace and that the support may be...

@Zanadar this issue was more in regards to documenting go code packages. I've updated the description with an example for better clarity. @ameyer-pivotal, feel free to provide additional clarification if...

@natalieparellano It looks like `io.buildpacks.lifecycle.apis` is up and coming from the [builder 0.1 spec](https://github.com/buildpacks/spec/blob/extensions/builder/0.1/extensions/builder.md#iobuildpackslifecycleapis-json) release so we don't technically have it yet. Good call out though. Until that is released...

@natalieparellano Is there a contract/spec provided for lifecycle images? I just now realize that you were talking about the lifecycle image which is interesting because AFAIK, that isn't spec'd making...

Given that neither set of labels and supported APIs were spec'd, I'm comfortable with moving to using the new label. Additionally, for context we are specing this out via the...

> @jromero I Want to try to solve this can you please assign this to me and point out some resources to solve this issue > Hi @basit9958 , Thank...

Hi @basit9958, wanted to check in since we last chatted on Slack. Is there anything we can do to further assist?

We should discuss this in a sub-team sync when @micahyoung is present.

Waiting on platform sub-team RFC from @micahyoung on this.