@witty-crayon-22786 given your suggestion about

./pants fix

replacing

tailor

and parts of

update-build-files

...should we add this goal in Pants 2.8 and switch autoflake and pyupgrade to use it, rather than

fmt

? Seems like we need to get that right before stabilizing those new features in Pants 2.8

maybe. but i also feel like 2.8.x is already huge, and we would be fine just not emphasizing those new backends yet

We've found in our release blogs that mentioning other popular tools has been extremely helpful in getting out the word. I think it would be a missed opportunity to not highlight Pyupgrade and Autoflake

we can, but we can just wait until we have a clearer story, imo.

Also, it's not yet a breaking change to add

fix

. No Pants 2.7 functionality would be impacted by that change. As soon as we stabilize Autoflake and Pyupgrade, switching from

fmt

to

fix

becomes a breaking change

then maybe one answer is to mark them

experimental

.

Sure, I'm okay with that!

basically, i think that if we were at three weeks in this cycle, the answer would clearly be to rename things