Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Should [status-completed] be used before the changes are live?
As of the time of writing, this request has the [status-completed] tag despite the change not being live yet. It is completely developed, sure, but since it is not yet deployed, should the request be marked completed?
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
A tag on the community meta should reflect the status as experienced by the community. A change in tag should communicate a change in experience. This allows users to provide feedback (it's working, it's not) rather than being unsure whether or not the new functionality is live because it might still be living in deployment limbo.
Comparing timestamps on deployment and update is non-intuitive. We should follow the principle of least astonishment and let status-complete mean complete from the view of the end user.
[status-completed] gets added once the code has been written, reviewed, and merged - i.e. is ready to deploy. Once [status-completed] has been added to a post, you can assume it'll be deployed in the next build - you can tell whether that's happened or not yet by comparing the timestamp on the answer with the timestamp of the build hash in the footer.
0 comment threads