Recommandé
Contenu connexe
Similaire à I wanna' help but jira scares me....
Similaire à I wanna' help but jira scares me.... (20)
Dernier
Dernier (20)
I wanna' help but jira scares me....
- 1. I Wanna Help, But JIRA Scares Me & Getting My Own Tomcat Seems Dangerous Matt Clare, Brock University @mattclare - Matt.Clare @ Brocku.CA http://go.mattclare.ca/jasigsakai12 June 10-15, 2012 Growing Community; Growing Possibilities
- 2. Non-Code ways to contribute 2012 Jasig Sakai Conference 2
- 3. The Plan How Where Tools More discussion 2012 Jasig Sakai Conference 3
- 4. How 2012 Jasig Sakai Conference 4
- 5. Types of contributions at an individual scale Quality Assurance (QA) and Feature Requests Visual and textual contributions Mentoring others or answering questions Advocacy Community strength and participation Something not listed here? 2012 Jasig Sakai Conference 5
- 6. Where 2012 Jasig Sakai Conference 6
- 7. Where 2012 Jasig Sakai Conference 6
- 8. Confluence:confluence.sakaiproject.org 2012 Jasig Sakai Conference 7
- 9. JIRA (bugs & features): jira.sakaiproject.org 2012 Jasig Sakai Conference 8
- 10. collab (mailing lists): collab.sakaiproject.org 2012 Jasig Sakai Conference 9
- 11. Twitter: A lot happens here... and doesn’t 2012 Jasig Sakai Conference 10
- 12. Where you work and live 2012 Jasig Sakai Conference 11
- 13. Tools Systems and processes 2012 Jasig Sakai Conference 12
- 14. Quality Assurance (QA) and Feature Requests 2012 Jasig Sakai Conference 13 confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines
- 15. Issue Types Bug - An error in design or implementation which directly impedes a user from achieving their expected result. Task - A new capability being added to Sakai. Feature Request - A desired capability, for inclusion in a future release of Sakai; ideas that come with resources interested in implementing them are more likely to be developed than those offered with the hope that someone else will step forward to do the work. Contributed Patch - A community-contributed patch to a particular version of Sakai. The origin of such issues may lie in Bugs or Feature Requests which Sakai has not yet evaluated for implementation. Under such circumstances a linked issue is generally created by cloning the original issue in order to track Sakai's work on the issue. [Use at your own risk!] 2012 Jasig Sakai Conference 14
- 16. Creating a Jira account 2012 Jasig Sakai Conference 15
- 17. Creating a Jira account 2012 Jasig Sakai Conference 15
- 18. Creating a Jira account 2012 Jasig Sakai Conference 15
- 19. Creating a Jira account 2012 Jasig Sakai Conference 15
- 20. A Feature Request https://jira.sakaiproject.org/browse/SAK-19912 2012 Jasig Sakai Conference 16
- 21. A Bug https://jira.sakaiproject.org/browse/SAM-1249 2012 Jasig Sakai Conference 17
- 22. Creating Issues 1. Verify it is not a local issue 2. Search JIRA to see if the issue already exists Search strategies include searching for a particular component, sorting by update date, and exporting as an MS Excel file (in Views) 3. User searches the sakai mailing lists archives • Searching nabble sakai-dev archives may help if you get too many results 4. User creates an issue in Jira of the appropriate • The component should be set based on where the problem appears to exist • The Assignee should be left as -Automatic- • The Affects Version should be set to the released version of the instance of Sakai being used. • The Fix Version should be left set to the default of Unknown. The project teams will set the Fix Version once they have had time to review the issue and estimate when they believe they will be able to address it. • As much of the following information should be included as possible (to avoid the issue being closed as incomplete) • (bugs) Steps to reproduce (detailed and step by step) • Environment details (DB type and version, tomcat version, OS type and version, Browser and version, etc.) • (bugs) URL to the page where the error occurs • (bugs) Stacktrace (traceback) if available • (bugs) relevant portions of the server logs (do not attach your entire logs, we do not have time to read through 1000s of lines of logs and figure out where the relevant parts are) • Screenshots showing the error • (feature) Use cases and detailed requirements • The desired resolution 2012 Jasig Sakai Conference 18
- 23. Watch/Vote 2012 Jasig Sakai Conference 19
- 24. Watch/Vote 2012 Jasig Sakai Conference 19
- 25. Confluence 2012 Jasig Sakai Conference 20
- 26. Confluence 2012 Jasig Sakai Conference 20
- 27. Confluence 2012 Jasig Sakai Conference 20
- 28. Confluence 2012 Jasig Sakai Conference 20
- 29. QA Servers 2012 Jasig Sakai Conference 21
- 30. QA Servers 2012 Jasig Sakai Conference 21
- 31. QA Servers 2012 Jasig Sakai Conference 21
- 32. Screenshots & Stacktraces 2012 Jasig Sakai Conference 22
- 33. Screenshots & Stacktraces 2012 Jasig Sakai Conference 22
- 34. Twitter https://twitter.com/#!/mathplourde/sakai 2012 Jasig Sakai Conference 23
- 35. Twitter https://twitter.com/#!/mathplourde/sakai 2012 Jasig Sakai Conference 23
- 36. Working with others 2012 Jasig Sakai Conference 24
- 37. Working with others 2012 Jasig Sakai Conference 24
- 38. Comments, Questions, Discussion ..... corrections? 2012 Jasig Sakai Conference 25
Notes de l'éditeur
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- A user (anyone) creates an Issue (please see #Create Issue Detailed Instructionsfirst)\n Issue is automatically assigned to a Awaiting Review status\nCLE team member verifies the issue for accuracy (i.e. is it an actual issue) and completeness of details.\n Complete and valid issues are set to status Open and assigned to a user or group (e.g. Samigo Team or CLE Team) who can resolve it.\n The team member may resolve the issue as Duplicate, Incomplete, or Cannot Reproduce if appropriate (see #Resolution).\nAssignee selects Start Progressand begins to work on the issue (as time and priorities allow)\n Assignee selects Stop Progress if they are not going to work on the issue anymore for a few days and it is not resolved\nAssignee sets the issue to Resolved with the relevant #Resolutionwhen work is completed\n For tasks, if there is nothing explicit for the QA team to test, then the issue is Closed without testing.\nQA team selects Start QAand begins verifying the issue\n QA team member selects Stop QA if they are not going to complete the testing on the issue within a short time frame\nQA team verifies resolution of the issue and adds a comment with details of the testing results and process.\n If verification fails, then it is Reopened for further work (automatically re-assigned to the user who resolved it)\n If verification succeeds then QA marks the status as Verified (indicating it has been Tested)\nRelease Manager merges the issue (if it is a bug) to previous supported and affected releases\n The associated version merge status is set to Resolved\n The issue is Closed by the Release Manager when the last merge has been completed\n\n
- Issue is vetted for accuracy, completeness of information, relevance to Sakai's overall design, etc.\n A good Feature Request should explain clearly what a user is trying to achieve. Use cases and scenarios can be helpful in communicating that.\nAssigned to appropriate Project Team or Working Group lead, The will evaluate and discuss such issues periodically, when the group reaches an appropriate point in the release cycle to adsorb community input.\n If the decision is made to not address the issue, then it should be resolved as "Won't Fix" with appropriate comments.\nWhen a project team is ready to address the issue, it should be Moved to a Task and an initial estimate of the Fix Version set.\n\n
- \n
- \n
- \n
- My successful feature requests (with bounty): https://jira.sakaiproject.org/browse/SAK-19912\nGiulia’s image https://jira.sakaiproject.org/browse/PRFL-393?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab \n
- \n
- \n
- \n
- \n
- \n
- \n
- You can create an account or use admin/admin\n
- You can create an account or use admin/admin\n
- \n
- https://twitter.com/#!/mathplourde/sakai\n
- \n
- \n