%general-entities; ]> Here is a summary list of things to do before committing changes: Test the instructions you are adding. Update general.ent with the new date. Update chapter01/changelog.xml. Check that all relevant files have been svn add'd or remove'd. Check the validity of the XML. Check that the book renders properly. Commit it. Update trac to reflect the changes. You should normally restrict a revision to one set of changes, so if you are updating the versions of three packages you will usually do that in three separate revisions. Also, general updates are normally made to the trunk and then merged to branches. Clearly, what forms a "set" is a matter for your judgement, but at least consider any likely impact on other current branches who may want to merge some or all of your change. The editors of the LFS book prefer that changes to the date in general.ent are made as part of a real change, even though this adds to what has to be done in a merge.