[maemo-community] Bugzilla 3.4 update

[From: Karsten Bräckelmann]

On Thu, 2010-09-02 at 17:42 +0200, Murray Cumming wrote:
> On Tue, 2010-08-31 at 18:43 +0200, Karsten Bräckelmann wrote:
> > This is my last day working part-time for maemo.org. I am sorry the
> > migration has been taking so long.
> > 
> > Bugzilla 3.4 can be found in trunk of the "bugs" garage project.
> >   https://garage.maemo.org/projects/bugs/

> This is a regular bugzilla 3.4.8 plus some changes, right? Can you
> briefly explain what changes you have made? (From now on, changes must
> be small with commit messages, of course).

Fortunately, there are hardly any code changes -- most of the custom
stuff now can better be implemented using existing upstream features.
Less hacks to maintain.

> Is there some documentation about how to deploy that code to the
> test.maemo.org?

Of course, this is fully documented -- though not publicly, because it
requires access to the raw bug database dump.


> > The maemo.org look-alike bugzilla skin has deliberately been designed
> > for easy maintenance of security updates later, and thus avoids changes
> > to the templates wherever possible. (Which means styling mostly is done
> > in pure CSS, not images.)
> 
> Is this the only reason for wanting to upgrade to bugzilla 3.4? What
> other advantages/features were we hoping for?

Well, it wasn't my call but I agree. The most important reason is that
2.22 has been EOL'ed long ago and doesn't get security fixes.

Besides that, it offers requested features, some fixes to bugs reported
against bugs.m.o and functionality to properly implement work-stream
(e.g. Brainstorm).


> > A test instance of Bugzilla 3.4 to play with is available to the
> > community on test.m.o. Mail sending has been disabled, and the database
> > snapshot is from mid Aug. [1]
> >   https:// test. maemo.org/ testzilla/
> > [1] URI deliberately spaced, no spiders and crawlers, please.
> 
> That certainly looks nice, fitting in well with the rest of the site.
> 
> > While I will no longer officially work for maemo.org, I am definitely
> > staying here as a member of the community.
> 
> David King might find some time to work on this, but it's not certain.
> First we need to establish the status of the current work and what
> should be done next.

-- 
Karsten Bräckelmann  -- lurker