Joomla! Issue Bug Tracking process
Joomla! Pizza Bugs and Fun event 17th Oct 2014 on Friday. Presenting Joomla! Bug Squad workflow and Bug tracking process to the world. It's an pre-event preparation for participating companies like Tailored Solutions Pvt. Ltd. iJoomer, xpertphp, Percept info.
2. Know about me...
• JUGAhmedabad Founder
• JBS Member
• Google Summer of Code
2014 Mentor
• Author in Joomla! Magazine
• Open Source Contributor
• And your Colleague...
Twitter: @ergunjanpatel Email: gunjan.ce2009@gmail.com
3. What is PBF – Pizza Bugs and Fun?
• Business level PBF
• Help Joomla!
• Give back to Joomla!
• An opportunity
• Know joomla! even more
• We – Tailored Solution Pvt. Ltd. participating as an
Epic - 100 hours, let’s do it. Let’s Make it happen.
4. Who can Join?
• Testers
• Frontenders
• Developer
• Project Managers
• Team Leaders
• Any Joomla! Or Web User can join....
5. Bug Tracking Process
• Testing Pre releases
• Reporting Issues
▫ Issues reported on the forum
▫ Issues directly reported to the tracker
• Issue Priorities
• Resolving Issues
6. Testing Pre releases
• Every great software need pre release testing
• Install current stable version
• Never test on Live or Production sites
• Set Joomla! Update Configuration => Test
• Install pre release testing pack when available and
test
8. Issue Priorities
1. Critical - The trunk is not working at all
2. Urgent - Serious issue or major loss in advertised
function
3. Medium - Issue is there but the application is still
working
4. Low - Minor loss
5. Very low - Misspelled words, Cosmetic Problems,
less common issues with parameters, graphically
misleading objects etc...
9. Resolving Issues
• Open/New – Just Reported
• Information Required – Need More info
• Needs Review – Need JBS/PLT/Experienced person to review
• Started – on discussion & between Open and Confirmed
• Confirmed – Bug found & need fix
• Pending – Code submitted & Need testing
• In Progress – working on pending code(Found issue in pending code)
• Ready to commit – Successfully tested by 2 people working fine
• Fixed in Git – Will be released in next Joomla!
10. Testing Pending issues
1. Install Component Patchtester from
https://github.com/joomla-extensions/
patchtester/releases
2. Select an issue and Apply Patch
3. Follow test instruction written in issue
4. Report your test results by mentioning `@test`
5. Revert Patch
6. Continue from step 3
Video: http://www.youtube.com/watch?v=4OWgusZgIfk
12. Submit a Bug Fix on Github - Developer
• Github Work Flow for Joomla!
• Basic CLI Commands to work with Git or any Git
client
• Joomla! Coding Standard
• Ask in Joomla! CMS Development Group
13. Github Work Flow for Joomla!
Official Joomla!
Repo
joomla/joomla-cms
Your Forked
Repo
gunjanpatel/joomla-cms
Local Repo
<local_path>/joomla
-cms
Local Path Example:
/var/www/git/joomla-cms
14. Basic CLI Commands to work with Git or any Git client
1. Fork Repository
2. Clone it
$ git clone <your_repo_url(forked)>
$ cd joomla-cms
3. Configure remote repository
git remote add upstream<remote_repo_url(From where you have forked)>
15. 4. Fetch change from remote and Configure local
working Branch
a) Working with new branch
$ git fetch upstream or git pull upstream staging
$ git checkout –b <fix_issue_#123> upstream/staging
b) Update exisitng branch
$ git fetch upstream
$ git merge upstream/staging
5. Add/Commit local changes
$ git add . or $ git add <file_name>
# To commit
$ git commit –a –m “[fix isse #1234] <Your Commit Message>”
16. 6. Push changes on origin – Your forked repository
$ git push origin <fix_issue_#123>
# or if you want to push in to different branch
$ git push origin <fix_issue_#123> :<different_branch_name>
7. Send Pull Request from Github
17.
18. Help
• http://docs.joomla.org/Bug_Tracking_Process
• Quick CLI Guide for GIT
http://bit.ly/joomlaGitCli
• For more details visit
http://docs.joomla.org/Git_for_Coders
• http://docs.joomla.org/Filing_bugs_and_issues
• Or Contact me