Dne 25.7.2010 21:55, Andre Klapper napsal(a):
I expected RHBugzillaPage to be a derived class of a generic Bugzillas extension class, but maybe I don't get the concept yet.
OK, couple of changes (I was more thorough on my blog http://mcepl.blogspot.com/ ... given the level of response I've got here):
- the official git repo (yes, git, I am not good enough for mercurial) is git://git.fedorahosted.org/bugzilla-triage-scripts.git - you need only Jetpack SDK (from http://hg.mozilla.org/labs/jetpack-sdk/ or from my Git mirror at git://repo.or.cz/jetpack-sdk.git)
git clone git://repo.or.cz/jetpack-sdk.git . bin/activate cd packages git clone git://git.fedorahosted.org/bugzilla-triage-scripts.git
and then you can run
cfx run
(on temporarily generated completely clean profile)
cfx xpi
makes you .xpi file which can be installed in your firefox as any other .xpi extension
This gives you the very bleeding edge whatever I have in repo. This is meant for developers. For users see below.
In GNOME Bugzilla stuff like the clickable "Stock answers" when you go on any open bug report is patched into the code on the GNOME Bugzilla server, see http://git.gnome.org/browse/bugzilla-newer/tree/template/en/default/bug/edit... and search for "addStockLink". I'm not aware of much other stuff that is used in GNOME Bugzilla, have to dive deeper into your docs to say more.
Of course, given my presentation is on GUADEC stock buttons on b.g.o are my biggest problem. Later if I found some other bugzillas I will look for some solution to this.
Stuff like sendBugUpstream() in RHBugzillaPage definitely looks useful for my work in bugs.maemo.org but so far I miss a basic introduction to the concept of all this (I suck in reading API docs because I'm a quite bad developer).
it collects all comments from the current bug and then fills in the upstream bugzilla with appropriate values (of course the description is just a concatenation of all comments, so it needs heavy editing)
I think I need more documentation to answer this (already starts at the very beginning: What to do exactly after checking out the hg repository and installing JetPack in Firefox by going to https://jetpack.mozillalabs.com/install.html to get this loaded and visible in a browser page, probably bugzilla.redhat.com?).
See above. We are in the later version of Jetpack development (we are in so called Jetpack-SDK, whereas you are talking about previous now abandonded Jetpack-prototype) which doesn't require special Jetpack extension to Firefox, but just to the contrary it generates Firefox extensions.
Many bugtriagers are no developers (I don't consider myself to be one either) and hence need an idiotproof how-to...
The above HOWTO is for developers of my extensions. As for users, I hope in future the HOWTO will be ... go to https://addons.mozilla.org/cs/firefox/addon/192496/ and install the extension. However, currently the one on AMO is not updated and not reviewed. Current latest .xpi (sometimes raw experimental) is at https://fedorahosted.org/released/bugzilla-triage-scripts/bugzilla-triage.xp... (semi stable releases are in the same directory and I hope to be able to make updates working before I get to AMO).
Also, some documentation seems vague (RHBugzillaPage/closeSomeRelease: "Auxiliary function to computer more complicated resolution" - what does that mean?)
RHBugzillaPage object is not meant for you. You can of course take whatever you want from it, but it is mostly intended as a superset for RH Bugzilla. I think you should be better with MozillaPage (set in the Configuration URL https://fedorahosted.org/released/bugzilla-triage-scripts/Config_mozilla.jso... to get Mozilla version which should be pretty plain one for you; and of course feel free to copy .json to your server and customize it to your heart's content).
Hope this initial feedback is helpful& see you at GUADEC!,
Yeah. Looking forward to see you!
Matěj