Javier Romero

This RFC might be of interest to this discussion as it would greatly improve performance: https://github.com/buildpacks/rfcs/pull/85 @chrono2002, it would be nice to have your thoughts there as well.

Now that the Lifecycle maintained by CNB has indefinite backwards compatibility support of Platform API versions should pack just always use the _latest_ released version by default?

Good call out. The consensus was that we should just use the latest available version of the lifecycle available. It _should_ be compatible with pack based on the ideals that...

Thanks @dmikusa-pivotal , you provided answers to questions that immediately come to my mind. It seems like this is a docker CLI specific implementation. I'd be okay with integrating with...

@leshik thank you for reporting this. It seems as though this would be a lower-level issue and not so much `pack`. Let me see if I can get other people's...

This may also be useful for the BuildKit integration. Specifically in removing the need to [reimplement export](https://github.com/EricHripko/cnbp/blob/main/pkg/cnbp2llb/export.go#L22-L25). It would require more thought but maybe the `export` phase could take an...

We had ZenHub managing epics. Since we stopped using it, I will add the issues to the description.

@jkutner What do we mean by MVP? I think only 2 tasks listed are future work, https://github.com/buildpacks/pack/issues/748 and https://github.com/buildpacks/pack/issues/749. The others probably need to get done to get a nice...

Further conversations on "MVP" occurred on: https://buildpacks.slack.com/archives/C01BMB6DXR8/p1601400706004100 You may join our slack via: https://slack.buildpacks.io

This is a very interesting set of errors. It appears as if our tests intended to make it so that certain files aren't writable are able to write in your...