Content from Exploring R's Bugzilla

Last updated on 2022-11-01 | Edit this page

Estimated time 25 minutes

Overview

Questions

  • Have you used or worked with Bugzilla before?

Objectives

  • Work with some simple functionalities of Bugzilla to create tabular/graphical reports.
  • Explore R's bug database.

Introduction

This lesson is divided into various challenges that you can try. Please refer to the Bugzilla webpage for all the challenges below.

Under construction!

Challenge 1: Locate the reports!

Once your are on the Bugzilla webpage, follow the instructions below to locate the reports:

  • Go to reports
  • Select Graphical Reports
  • Alternatively, you could select the Tabular Reports
  • Just ignore chart-specific instructions!

OUTPUT 

[1] "There will be a screenshot of the solution here. Will be added soon!"

Challenge 2: Understanding the Resolution tab!

  • On the horizontal axis, select Resolution
  • Go to the Resolution selection box, scroll to the end, press the Shift key as you click MOVED, so that all resolutions are selected
  • Click the Generate Report button to create a bar chart
  • Review the different resolutions
  • How many bugs are open (have resolution ---)?

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 3: Exploring a new report (Component)!

  • Start a new report
  • On the horizontal axis, select Component
  • Check the box to specify vertical labels
  • Select only Resolution --- and generate a bar chart
  • Discuss the results:
    • Which are the components with most/least open bugs?
    • What do all the components mean?
    • Which topics are you the most interested in?

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 4: Exploring another report (Version)!

  • Start a new report
  • On the horizontal axis, select “Version”
  • Check the box to specify vertical labels
  • Select only Resolution --- and generate a bar chart.
  • Discuss the results:
    • What is the oldest version of R in an open bug report?
    • What year was this from?

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 5: Walkthrough one more report (Status)!

  • Start a new report
  • On the vertical axis select Status
  • on the horizontal axis select Number of comments and generate a Line Graph
  • Discuss the result:
    • what can you infer from this summary?

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 6: Bonus Challenge!

Will be added soon! You can add a line with at least three colons and a solution tag.

Keypoints

  • Use the Bugzilla webpage to complete the exercises in this lesson

Content from Searching bugs on Bugzilla

Last updated on 2022-11-01 | Edit this page

Estimated time 25 minutes

Overview

Questions

  • Have you tried searching bugs on Bugzilla before?

Objectives

  • Before reporting a bug in R, we should first check if it has already been reported in Bugzilla
  • Learning how to search a bug that is already reported on Bugzilla

Introduction

This lesson is divided into challenges that help you to understand how to report a bug related to using rbind() with data.frames.

Under construction!

Challenge 1: First attempt at searching bugs!

Once your are on the Bugzilla webpage, follow the instructions below to locate the reports:

  • Search rbind data.frame using the search box in the navigation bar of Bugzilla
  • How many bugs are returned?

OUTPUT 

[1] "There will be a screenshot of the solution here. Will be added soon!"

Will be added soon! You can add a line with at least three colons and a solution tag.

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 4: Bonus Challenge!

Can you get Advanced Search to return the same results as Challenge 1?

Will be added soon! You can add a line with at least three colons and a solution tag.

Keypoints

Content from Browsing bugs on Bugzilla

Last updated on 2022-11-01 | Edit this page

Estimated time 45 minutes

Overview

Questions

  • Have you tried browsing the bugs on Bugzilla before?

Objectives

  • If you want to contribute by reviewing or fixing a bug, you need to find bugs that need attention and that you may be able to help with.

Introduction

This lesson is divided into several challenges that help you with browsing bugs on Bugzilla.

Under construction!

Challenge 1: Selecting a topic of your interest!

Once your are on the Bugzilla webpage, follow the instructions below to select a topic of your interest:

  • Select Browse from the menu
  • Look at the topics in R product category
  • Select a topic you are interested in/feel comfortable with.

OUTPUT 

[1] "There will be a screenshot of the solution here. Will be added soon!"

Challenge 2: Filter out a few items!

  • Scroll to the bottom and use Change Columns to remove Product and Resolution
  • Add Opened and Number of comments

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 3: Order the bug reports!

  • Order the bug reports by date
  • Keep the most recent at the top

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 4: Categorising the bug!

  • Pick a bug with 3-4 comments (one that has received some response)
  • Discuss your observations - can you categorise it as one of the following:
    • Bug Reporter misunderstands the function/documentation
    • Bug can not be reproduced.
    • Cause of bug is still being worked out.
    • Fix to bug is still being worked out/under debate.
    • A solution has been proposed by Bug Reporter or a Bug Reviewer and is waiting approval from R Core.
    • An R Core member has committed to implement the fix, but not yet done this.
    • Something else - please specify!

Will be added soon! You can add a line with at least three colons and a solution tag.

Challenge 5: Categorising the bug according to what action needs to be taken next!

  • Pick a bug with 1-2 comments (one that has had little response)
  • Discuss your observations - can you categorise it as one following, according to what action needs to be taken next?
    • Bug is actually a wish list item (suggested new feature) and should be recategorised/discussed.
    • Bug needs a (simpler) reproducible example.
    • Cause of bug not clear from report and needs investigation.
    • There is a proposed fix from the Bug Reporter that needs to be checked and reviewed.
    • Needs input on best way to fix from Bug Reviewer or R Core member.
    • How to fix is clear, but there is not yet a patch or commitment to fix.
    • Bug report has received a negative response (not a bug/not a welcome change) and should be closed.
    • Something else - please specify!

Will be added soon! You can add a line with at least three colons and a solution tag.

Keypoints