[Bug Bugzilla/31546] Bugzilla upgrade

["mark at klomp dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31546

--- Comment #5 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Frédéric Buclin from comment #4)
> (In reply to Mark Wielaard from comment #3)
> > We can use this bug to make sure all patches/features we need/want are in
> > 6.0.
> > Like the patches mentioned in this bug and things like the RH sitemap code.
> 
> If there are specific features you want, and if they are not too invasive,
> they could easily be implemented with the current version of Sourceware
> Bugzilla. Please file separate bugs using Product:sourceware
> Component:Bugzilla (not Infrastructure) and I can look at them.

Thanks. I forgot there was a specific bugzilla component. I set the component
of this bug, bug #29645 and bug #30610 to bugzilla now. Not sure those are not
too invasive and easy though.

> One example
> which comes to mind is inline history. See how I did it for Mageia Bugzilla,
> which is also running 5.0.4:
> 
> https://gitweb.mageia.org/web/bugs/commit/?id=8d9c748a5e694fb544c082128c9756a0ca702334

Nice. And especially nice mageia is also using 5.0.4. So we can easily share
patches. The patches I picked up from gentoo from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108473 were a bit of a pain
because they are using 5.0.6.

Like them we should also publish our bugzilla git repo.

Is this inline history patch also upstream? And if so, in which version? 5.2 or
6.0?

> (Note that I managed to loose my old SSH key when I bought my new PC, and so
> I can no longer access sourceware.org using ssh. Someone from overseers
> would have to help me if you want me to help with Bugzilla.)

I'll sent a private email to set that up. Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.