We might keep it in the tree with other LibreOffice code, but it's a separate application that doesn't provide any of the functionality of LO. Technically speaking, the AIR is not LibreOffice. > c) May be we worry other users with a separate product. I'm not sure that such a setup is going to be easier for an Ordinary User or for us. This sounds like we're trying to shoehorn multiple different projects into a single Bugzilla project, and it sounds very confusing to me. > Sub Compo: ImpressRemoteControl (We would ask for 2 new OS) > May be we will get other LibO-Related, but not LibO tools (Like Florians > b) do we need something so specific? What's with an iPhone / blackberry That of course includes: Ordinary Users, Devs, QA, etc. In my mind, the primary consideration is: How easy is it for users to interact with our infrastructure? I'm not sure that the total # of reported bugs should be our deciding metric. > Currently we've got 9 reported between. > if we do not get at least 60 Bugs /year (1/week) > a) do we have enough Bugs? I don't think that we need something like that > Currently I am a little doubtful that an own Component is really necessary > Summary: "Android V1.0.2: Automatic silent profile smartphone toĭ5) Existing bugs will be amended, Versions deleted, and BSA would work )ĭ4) In Bugzilla Component text and BSA we ask reporter to add his Version (or may be only Impress Remote Control, see below?)ĭ3) We think about Sub components (may be Android, iPhone. If B we would get back the version problem we currently have with ProductĬ) May be we worry other users with a separate product. Sub Compo: ImpressRemoteControl (We would ask for 2 new OS) May be we will get other LibO-Related, but not LibO tools (Like Florians Ī1) An how (if) will be divide that into Sub components?ī) do we need something so specific? What's with an iPhone / blackberry remote? If we do not get at least 60 Bugs /year (1/week)Ĭurrently we've got 9 reported between.
We should discuss here what exactly we want to do, and if it's a new Product (may be additionally new OS?) we can shift it to Tollef and ask him to proceed.Ĭurrently I am a little doubtful that an own Component is really necessary and appropriate:Ī) do we have enough Bugs? I don't think that we need something like that
#BUGZILLA CREATE NEW PRODUCT ANDROID#
This is a spin off from " Bug 60766 - BUGZILLA: Remove Android Impress Remote Versions". Know anyone who would like to learn Bugzilla for enhancing their skills? Let them know by sharing this article on Facebook, Twitter, or Google Plus. Have you tried Bugzilla? Share your experience in the comments below. In my next post, will learn about how to use the browse option to locate the bugs belongs to a specific product and component. You have successfully created a bug in bugzilla:) If you scroll down a bit, you will have additional options to change the status of the bug, add additional comments and finally save the changes. If your not sure what should be entered in the field, just click the label of the field that will navigate to the page where it describes the fields of the bug. Users will also have other options to add additional information about the bug like Milestones, Tags, URL, Deadline, CC List, Bug history,etc. Step 5 : #33781 bug is created successfully.
While you enter a summary of the bug, it will also show you the possible duplicates based on the keyword you enter.Īdd an Attachment to the bug by clicking the add an attachment button.Ĭhoose file and Enter description for the attachment in the space given. While submitting the bug should not leave those fields blank. Note : Required fields are marked with *. Step 2: In the next window, first select the pre-defined product classification and next select the product of your choice from the product list. Step 1: Click New in the Bugzilla Main-page Log in to the account with your credentials. Pre-requisite: If you don’t have a Bugzilla account create one here Create Bugzilla account.
#BUGZILLA CREATE NEW PRODUCT HOW TO#
Hey guys, in this post will learn about how to create a bug in Bugzilla.
0 kommentar(er)
