Hi Patrick,
Please see my inline comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 11.04.2016 um 22:18 schrieb Patrick Pollo Guilbert:
Hi Oomph-dev,
I think it would a good idea to have a bugzilla component for the Oomph wiki/documentation. For instance, this bug
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=442353) has been resolved by modifying the UI a bit but the
documentation and pictures aren't up to date yet with the changes. My guess would be that those can be updated only
when big releases happen, but what if some errors slipped by? What's the best way to report wrong/deprecated
documentation on the website or in the wiki?
I've just added a "Docs" component n bugzilla. Thanks for pointing it out ;-)
Platform (https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Platform) has components for both doc and
website. I think Oomph would only need one, but that's just an example. Tracecompass also has a website component for
reporting website errors/bugs (https://bugs.eclipse.org/bugs/describecomponents.cgi?product=Tracecompass).
I agree, one is enough.
Maybe a component already exists for those kind of issues, but it's not very clear to me... Should it be reported in
the Release Engineering component? Or maybe the Utilities? etc.
What do you guys think?
BR
Patrick
_______________________________________________
oomph-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/oomph-dev
