What is trac and how do I use it?
Ah, the trac system. Trac is a program on the server that keeps a record of every single code change made by the devs. It also serves as a bug reporting and archiving tool. Every time a change is made to the codebase, it is submitted to trac. When you read about “development version” or “bleeding edge code” this is the repository that people are referring to.
Initially, it can be quite confusing to move around and find things. The main area that you will probably use is located in the link along the top right of this screen. Choose “Browse Source”, then the “trunk” folder, and you’ll see what looks like a directory structure of the whole program. Next to each file name is a line with the most recent reason for the last change to that file. There is also a column to show the last time that particular file was updated.
Before you click anywhere, scroll down to the very bottom of the page. See where it says “download in other formats”? The zip archive link below is indeed a zip of the latest development version. It’s handy if you need or want the absolute latest version that hasn’t appeard on the official download page yet.
The same is true for individual files. You can always browse to your needed file and get a copy from the links at the bottom. Then you can integrate this into your install. Take care to read the comments next to the files, as sometimes there are warnings that it is still untested and should not be moved into a production site without a through test by you.
– how to file a bug ticket and follow the latest issues
– how to sync a local install with the latest version
– how to find line-by-line code changes
– how to get a zip of recently changes files
I’ll link to these as they are written.