Re: [Bugzilla]Documentation component?
On Mon, May 27, 2013 at 6:39 PM, RGB ES rgb.m...@gmail.com wrote: 2013/5/28 Rob Weir robw...@apache.org On Sun, May 26, 2013 at 4:13 PM, Ariel Constenla-Haile arie...@apache.org wrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. It ended up in Infrastructure/documentation. Not sure if that makes sense, but that is where it is now. Maybe better is General/Bundled Help ? Or a per-product component for the same? I think on a per-product basis is more clear and easier to find. OK. I've added a component called help with the description, Use this component to report issues related to the bundled help files . Regards, -Rob Regards Ricardo -Rob Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Bugzilla]Documentation component?
On Tue, May 28, 2013 at 10:38 AM, Rob Weir robw...@apache.org wrote: On Mon, May 27, 2013 at 6:39 PM, RGB ES rgb.m...@gmail.com wrote: 2013/5/28 Rob Weir robw...@apache.org On Sun, May 26, 2013 at 4:13 PM, Ariel Constenla-Haile arie...@apache.org wrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. It ended up in Infrastructure/documentation. Not sure if that makes sense, but that is where it is now. Maybe better is General/Bundled Help ? Or a per-product component for the same? I think on a per-product basis is more clear and easier to find. OK. I've added a component called help with the description, Use this component to report issues related to the bundled help files . Regards, -Rob Good...hopefully this will help Help :) Regards Ricardo -Rob Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- MzK You can't believe one thing and do another. What you believe and what you do are the same thing. -- Leonard Peltier
Re: [Bugzilla]Documentation component?
2013/5/28 Rob Weir robw...@apache.org On Mon, May 27, 2013 at 6:39 PM, RGB ES rgb.m...@gmail.com wrote: 2013/5/28 Rob Weir robw...@apache.org On Sun, May 26, 2013 at 4:13 PM, Ariel Constenla-Haile arie...@apache.org wrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. It ended up in Infrastructure/documentation. Not sure if that makes sense, but that is where it is now. Maybe better is General/Bundled Help ? Or a per-product component for the same? I think on a per-product basis is more clear and easier to find. OK. I've added a component called help with the description, Use this component to report issues related to the bundled help files . Great! Many thanks! Regards Ricardo Regards, -Rob Regards Ricardo -Rob Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Bugzilla]Documentation component?
On Sun, May 26, 2013 at 4:13 PM, Ariel Constenla-Haile arie...@apache.org wrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. It ended up in Infrastructure/documentation. Not sure if that makes sense, but that is where it is now. Maybe better is General/Bundled Help ? Or a per-product component for the same? -Rob Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Bugzilla]Documentation component?
2013/5/28 Rob Weir robw...@apache.org On Sun, May 26, 2013 at 4:13 PM, Ariel Constenla-Haile arie...@apache.org wrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. It ended up in Infrastructure/documentation. Not sure if that makes sense, but that is where it is now. Maybe better is General/Bundled Help ? Or a per-product component for the same? I think on a per-product basis is more clear and easier to find. Regards Ricardo -Rob Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[Bugzilla]Documentation component?
Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? I recommended to use code and write a tag on the summary like [Help] or [Documentation], but I'm not sure if this is the better approach. Note, under infrastructure product there is a documentation component, but everything on the infrastructure product points to the website, so almost nobody arrives there. Regards Ricardo
Re: [Bugzilla]Documentation component?
On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Regards -- Ariel Constenla-Haile La Plata, Argentina pgpvZXFcUfbcb.pgp Description: PGP signature
Re: [Bugzilla]Documentation component?
2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. The available products are App Dev Base Build Tools Calc Draw General Impress Infrastructure Installation Internationalization Math Native-Lang Writer Regards Ricardo Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: [Bugzilla]Documentation component?
On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpgWyK0XjG1H.pgp Description: PGP signature
Re: [Bugzilla]Documentation component?
On Sun, May 26, 2013 at 1:13 PM, Ariel Constenla-Haile arie...@apache.orgwrote: On Sun, May 26, 2013 at 10:04:57PM +0200, RGB ES wrote: 2013/5/26 Ariel Constenla-Haile arie...@apache.org On Sun, May 26, 2013 at 09:27:56PM +0200, RGB ES wrote: Recently, an user on the EN forum raised a valid question: which is the best way to report a bug not on how the program works but on the documentation? For example, Math have only two components, code and UI, but what happens if someone find an error on the bundled help? This used to be Product: documentation, Component: Online Help, as in https://issues.apache.org/ooo/show_bug.cgi?id=120194 Yes, but if you click on New to create a new issue the product documentation is missing. Yes, that's why the used to be ;) The option is also missing if you try to edit the product once created the bug. The category clean-up narrowed it too much, most of the bugs I submit end up in General - code. Regards -- Ariel Constenla-Haile La Plata, Argentina Is there no way to add Documentation back into the component list? -- MzK You can't believe one thing and do another. What you believe and what you do are the same thing. -- Leonard Peltier
