Pages that need work have an incomplete tag.
Pages that need to be deleted have a deleteme tag.
Pages that have problems with the citations at the bottom have the citations-incomplete tag.
Pages with comments that might make good sidebars are tagged as sidebar

review -> review + review-one -> review + review-two -> No tags
significant changes -> review or incomplete

There is some inconsistency with the use of const. We used to have a recommendation that declarations appear like this:

int const *ip;

But we eventually got rid of it. Most of our declarations are of this form, but some are of this form:

const int *ip;

The argument we had was that the first form is less prone to error, but the second form is widely used, and not something that people will change.

Our choices are a) apply the first style consistently, b) apply the second style consistently, c) allow a mix of both styles.

Whatever style we adopt should also apply to other qualified type declarations, like volatile.

The bot changes all of these to have rightmost const. There are very few (if any, it would only be what was added recently) the other way. -jp

Run spider with new changes.

C++ has it's own TODO List

Incomplete pages in Java use their own incomplete-java tag.

Pages now have tags to indicate the status of their corresponding checker in Compass Rose.
Complete rules are tagged rose-complete.
Partially complete rules are tagged rose-partial.
Rules that simply cannot be enforced by Rose or any other automated checker are tagged unenforceable.
Rules that can be easily implemented in Rose are tagged rose-possible.
Rules that have not been implemented in ROSE because they are already checked (partially or completely) by GCC are tagged rose-gcc.

It might also be worth giving these another look.