@ancient-vegetable-10556: good morning!

Hi!

my tack for nailing down the 2.15 MVP for https://github.com/pantsbuild/pants/issues/13682 is probably going to be documentation driven development: i worked through the case studies on Friday, and have a pretty good sense of what the use cases are and how to accomplish them. so i’m planning to sketch out environments documentation, full of TODOs which i’ll then turn into tickets if they’re not already covered.

Sounds good

in the meantime though, if you want to tackle Eric’s comment here: https://github.com/pantsbuild/pants/issues/7735#issuecomment-1261487016 , it should still all be accurate (although slightly affected by the changes in this section on Friday: https://docs.google.com/document/d/1vXRHWK7ZjAIp2BxWLwRYm1QOKDeXx02ONQWvXDloxkg/edit#heading=h.l8tbyq7h6zch )

Worth noting the changes in https://github.com/pantsbuild/pants/pull/17093 as they (slightly) change the environmentaware API

Worth noting the changes in https://github.com/pantsbuild/pants/pull/17093 as they (slightly) change the environmentaware API

sounds good… i don’t think that we’ll be documenting environments from a plugin perspective (yet) though, so shouldn’t impact

great