Sorry, but I disagree. status-completed implies that users will actually see the change, and it is is confusing in the interim between the "completion" and the "deploy" times.

@ArtOfCode I think that's fine for the dev team tracking their own progress in Trello. But for user-facing progress indicators--which these tags are--saying an item is complete before it's deployed is like announcing to a packed restaurant that desert is ready to be served, but by the way we won't actually bring it out to you for another few days.

I see the other post has now been updated with status-planned. I think that's a good approach. We can move it to status-completed after deploy.

@MonicaCellio - this is the post under discussion; it still has [status-completed]. (There's another, similar, request that's tagged [status-planned] because the PR hasn't been merged yet.)

I'd prefer the tag be premature (provided only very slightly) rather than be overlooked altogether. For me "will be live the next time a deploy happens" is good enough clarification for a short period. I imagine coupling the tag with the PR action makes it less likely it will be forgotten.

Furthermore, in many cases, the changes are currently being deployed, when we add the tag. Some exceptions exist, especially if it is a "minor" thing, where we deploy only once a few of them have been done,

I think that's fine if the tag descriptions clearly indicate that's what it means.

Downvote. Current behavior is confusing. Reasons:

1. Users don't know date of new deploy.
2. There are communities that don't related to development at all. How can they know what "deploy", "PR", "merged" mean ? I think that should be changed.