-
Notifications
You must be signed in to change notification settings - Fork 51
Development
theory edited this page Aug 16, 2010
·
2 revisions
These are the documents you should be familiar with if you intend to do Bricolage development. It’s not as overwhelming as it looks: Just start with something simple and work your way up!
- Community: Mail lists, IRC, etc.
- Working with Git: This will get you set up with a GitHub account, fork the project, and clone it to your local disk.
- Contributing a Bug Fix: Takes you through the basic steps to fix a bug in the master branch :formerly called trunk and push it up to GitHub.
- Working with Branches: How to go about working in a maintenance branch, such as rev_1_10.
- Merging with Git: Mostly about merging from a maint branch to master.
- Starting a Project Branch: For those of you who want to undertake some major hacking.
- Build Aliases: Useful shell aliases to quickly and non-interactively rebuild a Bricolage installation.
- Git Hacks: Cool tricks. Please add your own!
- Contributing via Email: In case you don’t want a GitHub account. Needs filling in by someone who actually decides to work this way.
- Creating a Release: How to create and test a tarball, where to upload it, and where to send announcements.
- Coding Standards: For Perl, SQL, in Emacs and Vim.
- Contributing Actions and Movers: Why don’t more people do this?
- Debugging: Tips to debug issues with Bricolage.
- Performance Tuning: Why is Bricolage going slowly? Tips to help you find out.