Since we right in the middle of deploying the 1.18 codebase to our
cluster, we need to make sure we're using tags in CodeReview in a
consistent way. After some discussion, here is what we've come up with:
1.18 - This should be backported to the 1.18 tarball release.
1.18wmf1 - This revision should be pushed to the cluster ASAP.
post118deploy - This revision should be pushed to the cluster, but
it can wait until the dust settles.
1.18ok - old fixmes that aren't a problem if they're deployed as
part of 1.18, but need to be fixed for 1.19.
*** Do not use this tag for any revisions after the 1.18 branch
*** point. We used this tag to remove fixmes from our list of
*** 1.18 deployment blockers, while still leaving them marked
*** "fixme"
revert1.18 - Stuff that needs reverting in 1.18
reverted1.18 - Stuff that was reverted in 1.18 but exists in trunk
Full list of tags:
http://www.mediawiki.org/wiki/Code_review_tags
Please avoid using the 1.18wmf1 tag unless it is directly related to a
regression from 1.17 currently visible on the cluster, or it is a very
major problem. If we can all use these tags consistently and
conservatively it will reduce the amount of stress our engineers suffer
during deployment.
Thanks,
Mark.