Discuss: Google Summer of Code Updates

[Son of a Beach]

When it comes to pruning revisions, it would be good to keep the first x revisions and the last x revisions and remove the ones (if any) that are in between. I can imagine that the first edition of a post in particular, is possibly the one you most likely want to see again in some situations.

Please don't just prune the oldest revisions, but allow the admin to specify the number of posts to keep from both the beginning AND the end of the revisions list.

[imkingdavid]

When it comes to pruning revisions, it would be good to keep the first x revisions and the last x revisions and remove the ones (if any) that are in between. I can imagine that the first edition of a post in particular, is possibly the one you most likely want to see again in some situations.

Please don't just prune the oldest revisions, but allow the admin to specify the number of posts to keep from both the beginning AND the end of the revisions list.

This issue has come up and I have decided to always automatically mark the first/original revision of the post as "protected", meaning that it will not be considered for deletion in the pruning tasks and will not count toward the number of revisions allowed on the post. I'm not sure that we need two more options to further limit it.

[Son of a Beach]

Sounds like a reasonable compromise. Thanks.

[EXreaction]

As long as a hook exists in the location where another post is added to the revision history, it would be extremely simple to more extensively control that if a board owner really wanted to.