A good (then lazy) coder will put valuable comments in his CVS commits. You'll see those comments in each post on cvs mails, if you subscribe to that list. Each change on the code source sends a mail to that mailing-list. It's a large amount of mails, but less than for devel list. A good way to follow development is also to update a local cvs version of tikiwiki. Use the command cvs log on a file gives out its history of all comments made on it. Very useful. Please add the tracker id number if you ar fixing a reported bug or a feature request.
- Get the cutting-edge-last-developers-version (updated every hour from a developer account) (5.8Mo)
- How to get a local CVS version of tikiwiki
If you want most recent CVS access, access CVS using SSH. If you want to do this automated using a cronjob, see here: Preventing CVS + SSH Password Prompts
- Subscribe to tikiwiki-cvs
- CVS howto for tikiwiki
- Naming convention for CVS Tags
- CVS comandlines for tikiwiki
- TikiWiki Changelog
- SourceForge WinCvs CVS Client Installation Instructions
CVS : what's that ?
It's a way to store code source and write it collaboratively. It's used in all open source projects and it's a must know.
- CVS Howto
- Quick reference to CVS
- Another Quick Reference to CVS
- CVS Best Practices
- CVS training
- CVS made simple on GNU/Linux
- CVS made simple on Windows
- How to Do Version Control with CVS