SymfonyCon Hacking Day

guidelines.md

Me and Luis Cordova have setup some guidelines for SymfonyCon Hacking Day.

We selected some tickets you can pick: https://docs.google.com/spreadsheet/ccc?key=0Ao1MtzhUynSNdE1HMVlpZV9DdHhxdGp0ZHc5Y0hpdEE&usp=drive_web#gid=3

1. Process to create a Pull Request

   • Fork the repository
   • checkout the right branch
   • reproduce the bug and create the failing test
   • Fix the bug and make sure the tests are passing
   • Run tests locally
   • Create PR to the branch you worked on and don’t forget to mention the original bug issue number

2. Process to reproduce bugs

   • Fork the repository standard edition repo
   • checkout the right branch
   • reproduce the bug
   • create a new branch with the code to reproduce the bug and create the failing test
   • Branch name convention <issue_number>
   • Create PR to the branch you worked on and don’t forget to mention the original bug issue number

Links for documentation:

• http://symfony.com/doc/current/contributing/code/patches.html
• http://symfony.com/doc/current/contributing/community/releases.html
• http://symfony.com/doc/current/contributing/code/git.html
• http://symfony.com/doc/current/contributing/code/bugs.html
• http://symfony.com/doc/current/contributing/code/tests.html

I would suggest to create tests BEFORE fixing the bug :) But don't want to be picky, important is to have tests!