AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Bugzilla open source1/28/2024 That document also explains how to upgrade Bugzilla to a new version, move a Bugzilla installation between machines, and migrate from other bug-tracking systems. Instructions on how to do this are in the Installation and Maintenance Guide. This is true of both stable and development versions. You would find that by clicking on the arrow next to the component, then picking "Recently Fixed Bugs in This Component": it will show a list of fixed bugs, you can pick one or more, then look at the attachments.By far best way to get, maintain and upgrade Bugzilla is as a checkout from the appropriate branch of our source code control system. Another pro-tip is looking at what other bugs in that same bugzilla product/component touched.This is highly effective! If the bug asks changing CSS files, for example, you could add a file filter like *.css in the top right. You can type some keywords from the bug at the top of the page and wait for the results in the codebase to come in. If the bugzilla bug doesn't mention specific files and you want to find out yourself without reaching out, your best ally is Searchfox.For bugs marked as "mentored", ask the assigned Mentor! If it's not in the bug, ask the reporter or the person responsible of that section of code.If all the above fails, you can rely synchronous communication and chat with the devs over here in the # developers channel.If the person is on bugzilla, the text field will autocomplete and show the relevant person. Type your question in the "Add comment" section, tick the "Request information from" checkbox and either pick the role of the person you want to flag from the dropdown, or select "other" and paste an email address there (that you have identified using the previous points). After logging into Bugzilla, on the specific page of the bug you need information on, scroll to the bottom. You can send direct request over Bugzilla to individuals, they are called "needinfo requests".You can find who to talk to based on where the code is/the bug was filed and then consulting this page. Mozilla publishes the list of folks who are responsible about components in Firefox.For this bugs, a "Mentor" is usually shown under "Assignee" in the "People" section of the bug.
0 Comments
Read More
Leave a Reply. |