summaryrefslogblamecommitdiffstats
path: root/computer/bugzilla-triage-scripts-ff-extension-for-ff4.rst
blob: 2216a1ed1afec94dbdbf3ee05ff71f12064df0b9 (plain) (tree)
1
2
3
4
5
6





                                                                    




























































                                                                                                          
                                                                             









                                                                                                             
                           

















                                                                                          
"So, where's bugzilla-triage-scripts FF extension for FF4, you ask?"
####################################################################

:date: 2011-03-30T02:12:00
:tags: bugTriage, jetpack
:category: computer

The great `Firfeox 4`_ is out_, and the official version of
bugzilla-triage-scripts_ is broken for you? I am sorry.  I have
a workaround for you, and working on the final solution of the problem.

Let me explain what’s going on in the back office::

   bradford:bugzilla-triage (next) $ git diff --shortstat maint
    58 files changed, 8284 insertions(+), 3375 deletions(-)
   bradford:bugzilla-triage (next) $

I have rewritten most of the code (almost no line went unseen). The main
change is that we are now using the official (not available when i wrote
the first version of the script) page-mod_ module. This required a lot
of work,  because page-mod provides isolated content-scripts which
cannot get directly to the main script (which has chrome-level
privileges), but they can only communicate in a very restricted manner
with the main script via messages. On the other hand set of content
-scripts share the same namespace, so inside of the scripts the
situation is much more simple. Aside from using the official environment
instead of my own hack (which I used before), the main advantage is that
the chrome-privileged part of the script is isolated from code of web
pages (and in the future it will be working even with Electrolysis),
that it should be possible to create unit tests for testing the script
(which would be awesome, my constant manual going to one particular and
hoping that's good enough testing is ridiculous; I have tried it and it
worked with much more simple `script for mass-closing of multiple
duplicates at once`_). While going through whole code, of course massive
amount of small bugs and typos was unearthed and fixed. I was working so
that I should be ready to release FF4 compatible version of my script in
the same moment FF4 would be released. However, then something happened
… Ehsan Akhgari `continued to work`_ on his (mostly b.m.o targetting)
scripts, and this time I have managed to get into contact with him, and
started to work on including his modules into mine. So, in the end I
cannot release 1.0 version of my scripts yet (which I hoped to do),
because they don't have enough testing and they don’t most of the stuff
i would like this release to have. However, given that my original
scripts (of FF3.\* era) are now completely broken on FF4, I have decided
what I have (without the Ehsan’s code), and so I have no three official
versions of my script:

1. `The version of the script`_ (numbered 0.27) working with Firefox
   3.6.\*. It is strictly maintenance only, bug reports are welcomed and
   they will be hopefully fixed fast, but no improvements or RFEs will
   be accepted.
2. `The version of the
   script <https://fedorahosted.org/released/bugzilla-triage-scripts/bugzilla-triage-latest.xpi>`__
   (numbered 0.92) which I originally thought to be 1.0. This is the
   script I used for couple of weeks with just small bug fixes, so I
   hope that it should be useful for general public. Of course, `bug
   reports`_ are very very welcome (Fedora login & password are
   required).
3. `The last version of the script`_ (currently 0.93, but expect
   updates). This version contains Ehsan’s scripts but with small fixes
   to make it work on Red Hat’s bugzilla. So, what can you expect to
   coming? For example this (it should be in future configurable, so
   only those who are interested, will use it):

.. image:: http://3.bp.blogspot.com/-06E4Umh1DJI/TZJzojD-dSI/AAAAAAAAAwA/vLHZuZiwgbk/s640/flag-hisotry.png
    :scale: 66%
    :align: center
    :alt: show proposal of elimination of multiple unnecessary status changes
    :target: http://3.bp.blogspot.com/-06E4Umh1DJI/TZJzojD-dSI/AAAAAAAAAwA/vLHZuZiwgbk/s1600/flag-hisotry.png

In the end I would need to introduce all functionality contained in
`Ehsan’s original scripts`_ (also described here_). Updates are not
working currently (if anybody is able to troubleshoot, any ideas are
welcome), but go and install and use the script.

.. _`Firfeox 4`:
  http://www.firefox.com/
.. _out:
  https://glow.mozilla.org/
.. _bugzilla-triage-scripts:
  https://fedorahosted.org/bugzilla-triage-scripts/
.. _page-mod:
  https://jetpack.mozillalabs.com/sdk/1.0b4/docs/packages/addon-kit/docs/page-mod.html
.. _`script for mass-closing of multiple duplicates at once`:
  https://gitorious.org/addon-sdk/mass-close-duplicates
.. _`continued to work`:
  http://ehsanakhgari.org/blog/2011-02-22/bugzilla-tweaks-getting-some-attention-again
.. _`The version of the script`:
  https://fedorahosted.org/released/bugzilla-triage-scripts/bugzilla-triage-latest-FF3.xpi
.. _`bug reports`:
  https://fedorahosted.org/bugzilla-triage-scripts/newtplticket
.. _`The last version of the script`:
  https://fedorahosted.org/released/bugzilla-triage-scripts/bugzilla-triage.xpi
.. _`Ehsan’s original scripts`:
  http://ehsanakhgari.org/blog/2010-01-07/bugzilla-tweaks-enhanced
.. _here:
  http://ehsanakhgari.org/blog/2011-02-22/bugzilla-tweaks-getting-some-attention-again